Print

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

[taskf53]

Thanks mates i tried but no go for me 

"something's f**ked up really bad" in my very old and very fat game 

[SAS~Storebror]

Just to be on the safe side, you didn't accidentally install the 4.09m addons?

[Bruno_Marc]

The game crashes as soon as I put a set of bombs. Without bombs, the plane starts. With a set of bombs, the game crashes.

[SAS~GJE52]

Then either ..

1. Don't load bombs


2. Post a log file as fas been clearly stated many many many times....


3. Get over it, stop whining and move on 

G;

[Bruno_Marc]

2020-01-30 04:43:01:219 (PipeLogger) : InstanceThread No.1: client disconnected.
2020-01-30 04:43:01:232 (PipeLogger) : InstanceThread No.1 terminating...
2020-01-30 04:43:01:241 (PipeLogger) : Log Writer No.1 terminated
2020-01-30 04:43:01:252 (PipeLogger) : InstanceThread No.1 terminated
2020-01-30 04:43:01:511 (PipeLogger) : il2fb.exe Termination detected, terminating Pipe Logger.
2020-01-30 04:43:01:521 (PipeLogger) : All Writers Threads finished, exiting.
Did you mean this code?

[Gubi]

Nope

[Bruno_Marc]

Nope

I already understood that. I installed SAS Common Utils. And it worked

[SAS~Storebror]

That issue of taskf53 still makes me wonder, so here's a list of things to do and check if you feel like taskf53:

• Make sure you didn't accidentally install the 4.09m Addons. As the name implies, they're for 4.09m and that means 4.09m only. You're on 4.12.2m, so these Addons aren't for your game version.
• With the Me-264 installed, open up air.ini and remove the line for the Me-264 (this effectively disables the mod). Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264" folder and remove all the files inside, but keep the folders inside. Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264" folder and remove the folders "presets" and "samples". Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264" folder and remove the folder "cod". Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264/3do" folder and remove the folder "Effects". Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264/3do" folder and remove the folder "Arms". Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264/3do" folder and remove the folder "Cockpit". Run the game and check whether it's working. If not, proceed...
• Open up the "#SAS/Me-264" folder and remove the folder "3do". Run the game and check whether it's working. If not, proceed...

It would be interesting to know at which step your game gets back to working state.

Once you have identified which of the contents had to be removed to get the game back working, reinstall the Me-264 and remove contents in opposite order so to make sure that it's really that content which you've just identified that caused the issue.
Then finally, reinstall the Me-264 again and remove only one single kind of content of the above mentioned list at a time, leaving everthing else where it is.

I know it's a lot I'm asking for, but I have to because there's two things that differ in dimensions between your game and everyone else's:

• You got the Bv-222 installed and running in Modact 5. No one else has.
• The issue you've reported is seen by no one else.

That's why no one else but yourself can do this test, sorry to say.


Mike

[Marat]

Dear Gentlemen,
As for me, I use Il-2 4.13.4 version with SAS Modact 6.4. Several month ago I installed BV-222 and it runs OK, but only if a mission starts in the air. Once landed and switched off engines, I can no more switch them on. Yesterday I tried to create a mission with BV-222 with taking off, but failed to switch on the engines. When using autopilot, the messages show only engine switching off, they fail to switch on. I will ask this question in BV-222 section.
I installed Me-264 and it runs OK as well. So, I mean both BV-222 and Me-264 can be used in my 4.13.4 with SAS Modact 6.4 with plenty of other mods

[Mission_bug]

Installed into my 4.12.2 with SAS ModActy 5.30, all looks good as far as I can tell from some rudimentary testing, thank you very much to all involved, really appreciated.


I also have the BV 222 working in the same installation, I only tried one of the Me-264 loads and that worked okay, my BV is set high in the #SAS folder '!_BV222', not sure if I altered that or it came that way in the download though.



Wishing you all the very best, Pete.

[dariofissolo]

I love it. Does it work on b.a.t?

[SAS~Storebror]

Just read a bit, the answer has been given in this thread already:

this beast and its weaponry seem to work just fine in BAT 3.7.2 with SAS Common Utils installed

the crew has 8 members - 9 jumps out of the plane

Confirmed, will be fixed in the next update.

Oxygen masks have only I and II pilot and dorsal gunner. Lack of navigator and rear armament operators (visible in the window).

That's intentional.
The crew in the rear compartment has a fully pressurized cabin and they're not deemed mission critical, hence the lack of separate oxygen supply.


Mike