Print

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

[SAS~Storebror]

Yeah, Steam can be a pita.
I don't have the Steam version of IL-2 myself so all I can tell is just hear-say.
Apparently in order to run modded IL-2 games it seems you have to install the Direct2Drive Patch:
https://www.sas1946.com/main/index.php/topic,1531.0.html

Other than that, it seems that Steam ships IL-2 with a custom il2fb.exe which cannot be restored by the Selector at the moment for the simple fact that I don't have it, so I cannot implement it.
This means that once you install a mod on your Steam game there's no way back to stock IL-2.
Therefore the recommended procedure is this:

• Reinstall/restore the IL-2 Steam version, should be possible from within the Steam app.
• Copy the whole IL-2 game folder (C:/Program Files(x86)/Steam/steamapps/common/IL-2 Sturmovik 1946 or something like that if you have Steam) to a different place (e.g. C:/Games/IL2/<call your version whatever you like here>).
  This will be the folder where you mod your game.
  Leave the stock game in it's Steam folder untouched.
• Apply Modact to the copied mod game folder.

Best regards - Mike

[Digital3d]

Thanks.
It works.

[Giuseppin]

A question: Why the british 500lbs bombs they have no fuze delay (nor low-level)? And Is there any way to fix this? Thanks in advance.

[SAS~Storebror]

Why the british 500lbs bombs they have no fuze delay (nor low-level)?

Sorry can't confirm, nothing to fix here:





Best regards - Mike

[Giuseppin]

Thanks, Storebor, and yes, the Blenheims they have fuze delay, but all others britsh aircrafts that can carry 500 lbs british bombs, don't have fuze delay: Beaufort, Hurricane, Mosquito, Swordfish, Wellington and Spitfire. Or at least I do not show me 

[SAS~Storebror]

Don't come back to list other planes now please, check yourself for issues in your particular game installation instead.
This is not a Modact issue, the reported "bug" simply doesn't exist.

Best regards - Mike

[Giuseppin]

OK, so the problem only exists in my game installation. Well, I will try to find out why. Strange, because in my VPmedia Modpack the problem is also reproduced. I guess it will be a conflict of mods. Thank you, Storebror, for clarifying this issue and sorry for making you waste your time.

[csvousden]

Giuseppin, you are not alone!  I just noticed that I have the same issue in my basic modded game 4.12.2, but that in CUP WAW it works fine.

Never saw that before.  Don't have a clue how to fix it, but wanted you to know you are not alone.

CV

[SAS~Storebror]

There's exactly two possibilities:
Either you installed a mod which replaces the new 4.12 style bombs with old pre-4.12 java code (old weapons mod anyone?), or you simply disabled bomb fuzes in the difficulty settings.

Best regards - Mike

[Giuseppin]

Giuseppin, you are not alone!  I just noticed that I have the same issue in my basic modded game 4.12.2, but that in CUP WAW it works fine.

Thanks CV. I fear that this problem is difficult to solve. And in my HSFX 7.0.3 installation I do not have this issue.

There's exactly two possibilities:
Either you installed a mod which replaces the new 4.12 style bombs with old pre-4.12 java code (old weapons mod anyone?), or you simply disabled bomb fuzes in the difficulty settings.

Best regards - Mike

No, Storebror. I´m sorry. I installed the 4.12.2m clean version, I checked in this version the issue and everything seemed right. Then I installed the VP Modpack and all mandatory patches (after all the VP Modpack is based on the SAS Modact 5.3.0, It is not like this?). I have not installed any mod or addon and voila! the problem appeared again. And of course I checked the difficult settings-bomb fuze and was activated. Thanks for your answers, Storebror.

[SAS~Storebror]

Let me summarize:

You installed 4.12.2 + Modact 5.3 and there's no issue.
Then you installed VP Modpack and the issue happens.

So far so good, I think every half-brained wanker got that this is not a Modact issue by now.

But... then you run to the next best IL-2 website and repeat blaming Modact for this?
---> http://www.mission4today.com/index.php?name=ForumsPro&file=viewtopic&t=21527

Mind you, there's many ways to show that you've lost the plot, this for sure is one of the fastest and most obvious.

Best regards - Mike

[vpmedia]

The guy who made this error report at m4t did not sound very upset so i doubt that he's blaming anyone.
His first statement was that he encountered this issue in SAS modact 5.3 and my modpack.

Question is why and how is this possible?
Only logical explanation to me is that he got a mod in SAS modact added which is also present in my modpack.

Second question is that do we know the name of the classfile responsible for bomb fuzes?