Print

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

[SAS~Storebror]

Should this work for maps aswell?

The short answer is: No.

You can add SFS archives to SFS_AUTO and replace existing stock objects appearance with the HSFX one, that's why we're talking about eye candy only.
If you want to add maps, you have to add and edit the regarding ini files as well.
And once you did so, you will notice that the maps have objects on them which are missing from Stock IL-2.
So you would have to add these objects, like buildings, runways, ships, tanks, cars etc.
When you got there, you'll notice that your missions still won't run because you're again using objects in your missions which are missing in Stock IL-2.
So back to start: Add all the missing objects, including java classes etc.
In the end you'd be asking for HSFX on 4.13.4, something that doesn't exist since 242 Sqn abandoned further HSFX development.

If you want to play HSFX, play HSFX.
If you want to play 4.13.4, play 4.13.4.
Both at the same time is a no-go.

Best regards - Mike

[Fadeev]

HD Skins:
HD Skins are not part of Modact 6.4x itself!
In order to enable HD Skins, please enable one of the HD DLL sets available in JSGME.
True Color Skins are part of the core game since 4.13.4.
To enable true color skins, please enable the difficulty option "Support for 24-bit skins (Beta)" in the "Misc" section of the difficulty settings in QMB or FMB.

Hi to all! HD skins (tested on 4K FW-190 skin) stopped working on my computer since 4.13.4. On 4.13.3 and 4.13.2 all was ok..
I have "classic modded IL-2" with "MODS". Game just crash when try to choose HD skin or dont see HD skin.

Have somebody tested HD skins in 4.13.4 already?

I've tried 24bit option from DT on\off, 24bit from "HD / True Color Mod v1.1 (4K Skins)" on/off... Also tried Alternative Versions 1 and 2 of HD skins *.dll files, no result

[SAS~Gerax]

Hi to all! HD skins (tested on 4K FW-190 skin) stopped working on my computer since 4.13.4. On 4.13.3 and 4.13.2 all was ok..

Double post ...  

[SAS~Storebror]

I have "classic modded IL-2" with "MODS".

Use Modact 6.4 and it works.
Modact is not "classic" game style.

Best regards - Mike

[Nephris]

.....
....
If you want to play HSFX, play HSFX.
If you want to play 4.13.4, play 4.13.4.
Both at the same time is a no-go.

Best regards - Mike

Thx got it 

[Fadeev]

I have "classic modded IL-2" with "MODS".

Use Modact 6.4 and it works.
Modact is not "classic" game style.

Best regards - Mike

Thank you, on Modact 6.4 all ok! 
Anyway I wonder what was the reason..

[SAS~Storebror]

The reason is that the Modact Java classfiles reside in the "#SAS" folder and they fix the remaining bugs in 4.13.4 concerning HD skins.
When you use the "MODS" folder instead, the new Java classes from "#SAS" folder will not get loaded, that's why HD skins won't work well.

Best regards - Mike

[Kelso]

The sfs files created in Total Modder 3.1 are not correctly read in game 4.13.4 with Mod Activator 6.4. Is there any advice on this?

[SAS~Storebror]

Nothing has changed for SFS files.
If they worked before, they will do so now.
What exactly isn't working for you?
Logfile?

Best regards - Mike

[Kelso]

Tiger Moth airplane mod - placed in #sas directory - works correctly. After packing to sfs file and placing in Sfs_auto directory - only horizon appears in game. Interestingly, the unpacked sfs file has the same contents as before packing. This is just an example. RRR Cyberolas Maps - the game does not see any new textures.

Edit: Stop - problem solved.

Edit 2: Mod Tiger Motch.sfs collided with Wheels by PA Jeronimo v.8.SFS. Cyberolas RRR maps.sfs collided with sas_maps_01.sfs

I'm sorry for the confusion - I did not do it for a long time  .

[SAS~Storebror]

In case of file content collisions, please remember that in contrast to the "#SAS" folder, where the first mod in alphabetical order overrides the others, for SFS files it's exactly the opposite: The last one rules!
For instance you have sas_maps_01.sfs and want to override some of it's contents, then your new SFS file would have to be named something alphabetically "behind" that name, e.g. "sas_maps_02.sfs" or "xx_sas_maps_01.sfs".

Best regards - Mike

[Kelso]

for SFS files it's exactly the opposite: The last one rules!

Thank you. I did not know that. Will be usefull...