Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SAS~Gerax]

Gerax, I have the engine mod listed before the US Marine Aviation Java Pack,
if this is wrong plz advise.

Doesn't matter as they share no classfiles.

Hint: use classchecker (find it here) to check if some mods
share classfiles with same name. This helps when struggling
with the always annoying question 'what should be loaded first'.

[VF19_Congo]

Thanks for enlightening me Gerax, much appreciated.
Your words hit home and I finally get it.
#SAS is simply another module.
So, to follow up, I could mod the #SAS module without affecting the others and so on?
At least to a point of some commonality ?

Nevermind, I answered myself

However, I have been launching from a shortcut to il2fb.exe, after, of course, changing to JTW module.
I made the assumption that "il2fb.ini" is being read because the il2fb.exe shortcut was loading JTW.
I now realise this  is probably bad practice, but was it actually working correctly or did I stuff up everything
so far by not launching through the launcher?

[SAS~Gerax]

or did I stuff up everything so far by not launching through the launcher?

No. Selector Manual tells us:

First Start
IL-2 Selector doesn't need to be run each time you want to run your game. You've got the
choice whether to run the game directly with current settings from the il2fb.exe.
....
or whether you want to launch the IL-2 Selector instead, usually for changing settings.
When you installed IL-2 Selector and run your game for the first time afterwards, please run
the IL-2 Selector at least once in order to adjust settings.
...

find the selector thread here and the manual here.

btw: there is a new patch by Western to the US MArine Aviation Java Pack here. 
 

[VF19_Congo]

Thanks again Gerax

I'm really a noob with IL2 modding, and slowly getting to know how things are put together,
however, there are a few unanswered questions I have, also some things are bugging me,
and I may as well get something off my chest right now.

I understand where a MOD folder in CUP, such as #JTW for example, might be disabled by renaming
the folder to  "-#JTW", as in a "restore point" temporary backup, (The IL-2 Selector expects to find #JTW).
Renaming folders to disable them has been part of my methodology for decades, however,
in the following context, you wrote:

Put this into your CUP-JTW directory and rename it so it becomes
first in load order (eg ! 00 ....).

Disable (put a minus ("-") in front of the mods name) "!SAS_Engine_Mod" in CUP-JTW.

Something here clicks in my brain ..... because the inference is a contradiction ..... as we are saying :

1.  Rename the folder to run it as a priority

and

2. Rename the other folder to disable it entirely.

I propose that such an action, as advised, may not have the desired effect and that both folders are
still active and loading.......

[SAS~Gerax]

...both folders are still active and loading.

No, they aren't.

Congo, just do a little test:
disable a planes mod with the minus in front..
and see what happens. 

You will get a CTD, and in the log you will find that the game
reads the entries in air.ini but doesn't find the planes classfiles.

And the same is true for mods without classfiles. They are ignored at startup.
Try a 3d-fix mod without classfiles with and without the minus - and see the difference ..

I do not know why its the minus, maybe this is declared in wrapper.dll?
Just wild guessing, I'm sure Storebror will know more...

update: just found an old text from 2009 where someone explained the wrapper.
And there I found this:

5 enabling/disabling mods :
wrapper does not load any folder which have "-" as prefix in its name ( "-Spitfire1" )
so to disable certain mod just place "-" in its folder name

[VF19_Congo]

Ah, ok, Thank you Gerax, silly me, I'll modify the previous post so it's not so much of a rave

[SAS~Gerax]

so it's not so much of a rave

Why a folder with a "-" in front is completely ignored by a modded IL-2 is a valid question.