[1.0] Reoccurring error slowing game down to 3 fps.

Started by Daelight, November 17, 2018, 04:42:15 PM

Previous topic - Next topic

Daelight

Heyo, one of my many mods are breaking my game and I have no idea why or which one is the culprit. The error in question happens after around 6 hours of gameplay, I tried starting over with a new colony, was fine until ~6 - 7 hours in. You can see the error at the bottom of my log file 

Here is a link for my latest save: https://mega.nz/#!sGolDSjQ!Vr34YwgijgdnGUzQq4jAM4YaESC7w3uv-LfEq5vEzcY

Here is the link for my log: https://git.io/fpnBd

Thank you for any help :^]

Razuhl

It's because the quest trader is going through the item definitions in your game and is finding an item definition that is invalid. Try booting Ed-Shields, it doesn't have an assembly and therefore the classes are missing when the buildings are loaded. Reinstall through steam, you probably downloaded the repository from github but not the actual release. You can also try deactivating RemoteTech and SupplyAndDemand since they work with trader stocks.

You can remove the incident from your save file if nothing else works but that will just put off the error for now. Search for "Quest_TradeRequest" and remove the red stuff that should avoid the error for now.

<storyteller>
         <def>Rainbeau</def>
         <difficulty>Rough</difficulty>
         <incidentQueue>
            <queuedIncidents>
               <li>
                  <firingInc>
                     <def>Quest_TradeRequest</def>
                     <parms>
                        <target>Map_1</target>
                        <threatPoints>-1</threatPoints>
                        <faction>Faction_176</faction>
                        <forced>True</forced>
                        <spawnCenter>(-1000, -1000, -1000)</spawnCenter>
                        <spawnRotation>2</spawnRotation>
                        <pawnGroups IsNull="True" />
                     </parms>
                  </firingInc>
                  <fireTick>3796200</fireTick>
                  <retryDurationTicks>2500</retryDurationTicks>
               </li>

            </queuedIncidents>
         </incidentQueue>
      </storyteller>

Daelight

Quote from: Razuhl on November 18, 2018, 01:35:49 PM
It's because the quest trader is going through the item definitions in your game and is finding an item definition that is invalid. Try booting Ed-Shields, it doesn't have an assembly and therefore the classes are missing when the buildings are loaded. Reinstall through steam, you probably downloaded the repository from github but not the actual release. You can also try deactivating RemoteTech and SupplyAndDemand since they work with trader stocks.

You can remove the incident from your save file if nothing else works but that will just put off the error for now. Search for "Quest_TradeRequest" and remove the red stuff that should avoid the error for now.

<storyteller>
         <def>Rainbeau</def>
         <difficulty>Rough</difficulty>
         <incidentQueue>
            <queuedIncidents>
               <li>
                  <firingInc>
                     <def>Quest_TradeRequest</def>
                     <parms>
                        <target>Map_1</target>
                        <threatPoints>-1</threatPoints>
                        <faction>Faction_176</faction>
                        <forced>True</forced>
                        <spawnCenter>(-1000, -1000, -1000)</spawnCenter>
                        <spawnRotation>2</spawnRotation>
                        <pawnGroups IsNull="True" />
                     </parms>
                  </firingInc>
                  <fireTick>3796200</fireTick>
                  <retryDurationTicks>2500</retryDurationTicks>
               </li>

            </queuedIncidents>
         </incidentQueue>
      </storyteller>

Hey, thanks for your help. I've tried re-installing Ed-Shields, removing Ed-Shields completely along with RemoteTech and SupplyAndDemand. Unfortunately none of that worked. Although removing the incident from my save did work. So I suppose I'll just do that whenever I get the error.

Again thank you very much for your help :^]