Jump to content

[1.7-1.9] SMURFF: Simple Module adjUstments for Real-ish Fuel-mass Fractions 1.9.1 (02019 Nov 12)


Recommended Posts

10 hours ago, Kerbas_ad_astra said:

And here we are with SMURFF v1.5, "Ore Rly?"

  • Ore tanks are now adjusted, baselined against 55-gallon drums.
  • Compatible with tank types included in Near Future Construction 0.6.2.
  • Added new "Extras" folder for patches that are too part-specific to be included in the main distribution. The first Extra patch is for the CryoX and soft tanks from Ven's Stock Revamp. I make no promises about their balance when used with CryoTanks or other fuel-switching plugins...

I've been working to set up a 10x game, and found this mod that will make my life easier.

 

Anways - I dropped in the current version and module manager is reporting 31 errors:

 

They all appear to be related to LH2 and FuelTanksPlus

 

Spoiler

[LOG 06:44:27.927] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.929] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size0/TPtank0mL00175/TPtank0mL00175
[LOG 06:44:27.930] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.931] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size0/TPtank0mL00700/TPtank0mL00700
[LOG 06:44:27.932] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.933] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size0/TPtank0mL01350/TPtank0mL01350
[LOG 06:44:27.934] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.935] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size0/TPtank0mL01875/TPtank0mL01875
[LOG 06:44:27.937] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.938] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPcone1m1/TPcone1m1
[LOG 06:44:27.939] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.940] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPcone1m2/TPcone1m2
[LOG 06:44:27.941] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.942] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPdome1m1/TPdome1m1
[LOG 06:44:27.943] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.944] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPtank1m0mA/TPtank1m0mA
[LOG 06:44:27.945] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.946] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPtank1mL00313/TPtank1mL00313
[LOG 06:44:27.947] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.949] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size1/TPtank1mL05625/TPtank1mL05625
[LOG 06:44:27.949] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.950] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPcone2m/TPcone2m
[LOG 06:44:27.952] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.953] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPdome2m/TPdome2m
[LOG 06:44:27.955] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.956] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPtank2m1mA/TPtank2m1mA
[LOG 06:44:27.957] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.958] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPtank2mL00469/TPtank2mL00469
[LOG 06:44:27.959] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.960] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPtank2mL05625/TPtank2mL05625
[LOG 06:44:27.961] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.962] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPtank2mL11250/TPtank2mL11250
[LOG 06:44:27.963] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.965] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size2/TPtank2mL15000/TPtank2mL15000
[LOG 06:44:27.966] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.968] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPcone3m/TPcone3m
[LOG 06:44:27.969] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.970] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPdome3m/TPdome3m
[LOG 06:44:27.971] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.972] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3m2mA/TPtank3m2mA
[LOG 06:44:27.974] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.975] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3m2mA2/TPtank3m2mA2
[LOG 06:44:27.976] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.977] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3mL00938/TPtank3mL00938
[LOG 06:44:27.978] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.979] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3mL05625/TPtank3mL05625
[LOG 06:44:27.980] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.981] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3mL11250/TPtank3mL11250
[LOG 06:44:27.982] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$
[LOG 06:44:27.983] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to FuelTanksPlus/Size3/TPtank3mL15000/TPtank3mL15000
[LOG 06:44:27.985] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$

 

[LOG 06:44:28.067] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]:HAS[@SUBTYPE[LH2]]]:FOR[zzz_SMURFF] to Squad/Parts/FuelTank/fuelTankOscarB/fuelTankOscarB/miniFuelTank
[LOG 06:44:28.069] [ModuleManager] Error - Cannot parse variable search when editing key modMass = #$/MODULE[ModuleB9PartSwitch]/SUBTYPE[LH2]/addedMass$

Link to post
Share on other sites

I need some more information on what other mods you have (e.g. cryogenic engines?).  Looking briefly at FTP, its fuel-switching patch doesn't create an LH2 tank type at all, so there must be something else at work.  I'm also not sure why the Oscar B but no other Squad fuel tanks would be affected.

Link to post
Share on other sites
10 minutes ago, Kerbas_ad_astra said:

I need some more information on what other mods you have (e.g. cryogenic engines?).  Looking briefly at FTP, its fuel-switching patch doesn't create an LH2 tank type at all, so there must be something else at work.  I'm also not sure why the Oscar B but no other Squad fuel tanks would be affected.

Yes, I have cryo engines and tanks.

Spoiler

 

Folders and files in GameData:
000_Toolbar
000_USITools
AllTheseWorlds
Arkas
AtomicAge
B9PartSwitch
BahaSP
BetterBurnTime
CoherentContracts
ColorCodedCans
CommunityResourcePack
CommunityTechTree
ContractConfigurator
ContractPacks
Crowd Sourced Science
CryoEngines
CryoTanks
CTTP
CustomAsteroids
CustomPatches
DarkSideTechnology
DeadlyReentry
DeployableEngines
DMagicOrbitalScience
DMagicUtilities
DSD
EveBiomesPlus
ExtraplanetaryLaunchpads
FerramAerospaceResearch
Firespitter
FuelTanksPlus
HeatControl
InterstellarFuelSwitch
JoolBiomes
JSI
KAS
KASE
KerbalAtomics
KerbalEngineer
KerbalJointReinforcement
kerbodynePlus
KerbolOrigins
KIS
Kopernicus
KSP-AVC
LETech
MarkIVSystem
MechJeb2
ModRocketSysLite
ModularFlightIntegrator
NavyFish
NearFutureConstruction
NearFutureElectrical
NearFutureProps
NearFuturePropulsion
NearFutureSolar
NearFutureSpacecraft
OPM
PreciseNode
ProceduralFairings
RCSBuildAid
RemoteTech
RoutineMissionManager
SCANsat
SentarExpansion
Sigma
SigmaDunaIke
SMURFF
SpaceY-Expanded
SpaceY-Lifters
Stock folder: Squad

StageRecovery
StationPartsExpansion
SurfaceLights
SurveyTransponder
TarsierSpaceTech
Trans-Keptunian
TriggerTech
UmbraSpaceIndustries
UniversalStorage
WillStr1
XPC
[x] Science!
ModuleManager.2.6.25.dll
ModuleManager.Physics
ModuleManager.TechTree
toolbar-settings.dat

 

 

17 minutes ago, Kerbas_ad_astra said:

  I'm also not sure why the Oscar B but no other Squad fuel tanks would be affected.

I think FTP adds an oversized oscarB.

Link to post
Share on other sites
2 hours ago, sentania said:

Yes, I have cryo engines and tanks.

Are you sure you have the latest versions of those?  Those MM errors mean that there's an LH2 tank type without an "addedMass" variable.  This was the case in a previous version of CryoTanks, but was changed in the version bundled with Cryogenic Engines 0.3.2 and Kerbal Atomics 0.2.2.

Link to post
Share on other sites

I'm getting some errors with the latest version that seem related to procedural parts:

Spoiler

[LOG 09:53:45.628] [ModuleManager] Applying node SMURFF/SMURFF/@PART[*]:HAS[@RESOURCE[Ore],~SMURFFExclude[*rue]]:FOR[zzz_SMURFF] to ProceduralParts/Parts/Tanks/TankOre/proceduralTankOre
[LOG 09:53:45.628] [ModuleManager] Cannot find key maxAmount in RESOURCE
[LOG 09:53:45.629] [ModuleManager] Error - Cannot parse variable search when replacing (%) key resourcemass = #$RESOURCE[Ore]/maxAmount$
[LOG 09:53:45.630] [ModuleManager] Cannot find key resourcemass in PART
[LOG 09:53:45.630] [ModuleManager] Error - Cannot parse variable search when editing key mass = #$resourcemass$
[LOG 09:53:45.632] [ModuleManager] Cannot find key resourcemass in PART
[LOG 09:53:45.632] [ModuleManager] Error - Cannot parse variable search when editing key reservedmass = #$resourcemass$

Guessing it can't modify the amount as it's generated procedurally?

Link to post
Share on other sites

It has a "RESOURCE{ name = Ore }" line with no amount or maxAmount.  That looks like a bug on their part -- the other procedural tanks have amounts given of their respective resources (presumably the default amount).

Version 1.5.2 is out!  (It was going to be 1.5.1, but then I realized that there is a procedural ore tank.)

From 1.5.1 (Mass Deregulation):

  • Relaxed one of the "overdraft protection" checks.

From 1.5.2 (Ore you sure?):

  • Added support for the procedural ore tank type.
Link to post
Share on other sites

Can SMURFF change engine atmosphereCurve?

I've added these:

Quote


@SMURFFCONFIG:FIRST
{    
······
    
    // *** ENGINES ***
    
    // For TWR, we want 1 to correspond to a 4x multiplication of TWR, and 0 to a "1x" multiplication.  It's exponential, so 0.5 will correspond to a 2x factor.
    
    enginemassfactor = 0.25
    @enginemassfactor != #$enginelever$
    
    enginethrustfactor = 3.0
    @enginethrustfactor != #$enginelever$
    
    engineISPfactor = 2.0
    @engineISPfactor != #$enginelever$

    
······
}

 

// **** ENGINES ****

@PART[*]:······
{
   ······
    
    @MODULE[ModuleEngines*]:HAS[@PROPELLANT[Oxidizer]],*
    {
        @maxThrust *= #[email protected]/enginethrustfactor$
@atmosphereCurve
        {
            @key = 0 *= #[email protected]/engineISPfactor$
            @key = 1 *= #[email protected]/engineISPfactor$
            @key = 3 0.001
        }

        
    }
    
}


 

But it doesn't do the trick. I think “@key = 0 *= #[email protected]/engineISPfactor$” is not correct. Will you help me with it? Thanks!

Link to post
Share on other sites

That's more of a Module Manager question -- check out this post for more details on how editing variables work -- but here's a quick explanation (I'm feeling a little fuzzy from the heat in my neck of the woods, so I'm sorry if I'm not entirely coherent).

To get what you want, it should be something like:

@key,0[1, ] *= #$whatever$

That is, calling out the "zero"th (i.e. first, because variables are zero-indexed by convention) variable called key, and then the second entry in that key variable (which is a space-separated list, hence the ", " in the brackets), and then multiplying that by your factor.  You can look at the SRB patches for an example.

The last entry really shouldn't have an "@" sign in front of it at all, since you're creating a new key with that one, right?

I'm curious -- why are you interested in doubling the Isp of bipropellant engines?

Edited by Kerbas_ad_astra
Link to post
Share on other sites
On 5/27/2016 at 0:42 PM, Kerbas_ad_astra said:

Are you sure you have the latest versions of those?  Those MM errors mean that there's an LH2 tank type without an "addedMass" variable.  This was the case in a previous version of CryoTanks, but was changed in the version bundled with Cryogenic Engines 0.3.2 and Kerbal Atomics 0.2.2.

I have the latest of both of those installed, I redownloaded them and checked to make sure cryotanks wasn't off, and am still getting an error.

Suggested next steps for digging?

cc:

@Nertea @NecroBones

 

Link to post
Share on other sites

Looking more closely at FTP, I think I see the issue -- FTP adds B9PartSwitch modules to achieve color changing, and then CryoTanks adds its own for the fuel switching.  SMURFF sees that the tanks have a B9PartSwitch module with an LH2 SUBTYPE, but because FTP's patches come first, SMURFF's patches try to dive into the color-changing patch, which doesn't have an LH2 SUBTYPE (which causes Module Manager to choke).  The fix is to specify in the patch.  Let me try it really quick.

Link to post
Share on other sites
  • 2 weeks later...

Latest Module Manager screams 10 errors with SMURFF config.

This cofing has [*rue] entries instead of [true], is this intentional?

First entry with this bug is like this:

@PART[*]:HAS[@RESOURCE[LiquidFuel],~SMURFFExclude[*rue]]:FOR[zzz_SMURFF]

Edit: Replaced [*rue] to [true] and still there are 3 errors.

Module Manager doesn't create logs or cache for weird reason (maybe because I'm using 64x bit/ directx 11 mode?)

 

Edited by raxo2222
Link to post
Share on other sites
6 hours ago, raxo2222 said:

This cofing has [*rue] entries instead of [true], is this intentional?

 

I often do the same thing. The reason for this is that it will accept both "True" and "true" (notice the capitalization difference).

Link to post
Share on other sites
1 hour ago, NecroBones said:

 

I often do the same thing. The reason for this is that it will accept both "True" and "true" (notice the capitalization difference).

Well module manager pukes with errors if you do that - 10 errors if its left as "*rue" (* can be any letter or symbol) or 3 errors if I change it to "true"

Link to post
Share on other sites

For the reasons that @NecroBones outlined, [*rue] is intentional and is almost certainly not the root cause of your problem.  It is most likely the case that some parts you have are missing some variables that SMURFF expects to be present.  This may be a problem with SMURFF (i.e. its expectation is incorrect) or a problem with some mod (i.e. it is not conforming to spec).

I need your KSP log (Module Manager doesn't make its own log, it adds entries to the stock log, and it also won't generate a cache if it has any errors) and the list of mods that you use to help you further.

Edited by Kerbas_ad_astra
Link to post
Share on other sites

Hey Kerbas, I'm currently having some issues with Module Manager throwing three errors during start up and they are with SMURFF, and I've narrowed it down to Procedural Parts. When launching the game without Procedural Parts, MM loads everything fine. I know a couple people having the same issue, but I also know people who don't have this issue. Any idea what could be causing this? Here's my output log with Procedural Parts installed. 

If anyone feels the need to tear apart this modlist and tell me anything that would help my save, go for it lol. I'm new to managing a large modlist, so any feedback is welcomed.

Also, since I couldn't copy paste I had to upload my output_log to my dropbox. Here it is WITH procedural parts. 

https://www.dropbox.com/s/62oluhgr17nvb42/output_log.txt?dl=0

 

 

Link to post
Share on other sites

PJ, the problem is the procedural ore tank I mentioned a little up the page. I'm not going to make the time right now to add logic to all of my patches just to catch one non-standard part (getting started with a new job).  Even the other procedural parts all have their default resource amounts defined, so I think the change should be made on their end.

@raxo2222, to be clear, please get me the log that results when you run the game with [*rue] -- I need to know what sort of issue it's causing and if it's something I need to fix.  Or maybe some mod maker added a line that says "SMURFFExclude = sprue".  :)

Link to post
Share on other sites
6 hours ago, Kerbas_ad_astra said:

PJ, the problem is the procedural ore tank I mentioned a little up the page. I'm not going to make the time right now to add logic to all of my patches just to catch one non-standard part (getting started with a new job).  Even the other procedural parts all have their default resource amounts defined, so I think the change should be made on their end.

@raxo2222, to be clear, please get me the log that results when you run the game with [*rue] -- I need to know what sort of issue it's causing and if it's something I need to fix.  Or maybe some mod maker added a line that says "SMURFFExclude = sprue".  :)

k

J4XgW3O.png

And there are logs (I quit game after it loaded) - 3 errors related to SMURFF.

http://www64.zippyshare.com/v/06kze51L/file.html

I play 64 bit version with - force d3d11 or like that.

 

Edited by raxo2222
Link to post
Share on other sites
  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...