Trouble with FMB
#1

Hi everyone

I know this has been mentioned in other places (Typhoon IB for example) but I thought it would be better to open this topic since it affects more than one aircraft mod.

Before the Universal Installer 1.1 was released, I had a problem using the PZL P.24 in the FMB causing it to crash. At the time I though it was a memory problem with my PC but now I see the same problem with several other aircraft.
I did a clean installation of Il-2 1946 followed by Universal Installer 1.1 (and later on the 1.1.1 update). I've added a few effects mods and aircraft like the Bf 109E-1 and then several others that have been released recently: F-80A, all of the Bf 109 sub-variants, Sabre, Sea Fury and F4U-1. I didn't install the P.24 because of the problem mentioned and besides I imagine work is still being done on the damage models (they sure take a lot of hits and still look immaculate!!). I haven't gotten round to installing the Magister.
To my dismay I found that the Bf 109E-3 also caused the FMB to crash. I've just been going through several aircraft and the list of aircraft affected therefore (and so far) is the following:

P.24
Bf 109E-1, E-1/B, E-3, E-3/B
Typhoon IB

Today I've increased my RAM so the problem wasn't there (as I imagined). I deactivated the various effects in the mods folders that I had installed but to no avail. I'm aware that not everyone has this problem but it would be very interesting to try and find out why this happens. Any pointers anyone?

I'll see if I have time to investigate further these days.
Reply
#2

mig88,

I also had the problem with the Bf109E-3, downloading and installing the updated "buttons" file by Maus solved this problem for me. However, I still have the problem with the Typhoon and Typhoon only. This is the only one of the newly released planes I am having a problem with. Becasue the problem I had with the 109E-3 was exactly the same as the Typhoon untill I updated the buttons file, Im wondering if the Typhoon might need to be added to the buttons file as well? Just a thought as its hard to see exactly whats contained in the buttons file, it is encrypted in hexidecimal and impossible to read with notepad or any other wordpad program.
Reply
#3

Fay King

That's odd because I have used both the "Almighty" and the UI1.1 version of the buttons!
Thanks for the tip anyhow. I'll look into it tomorrow.
Reply
#4

The crash with the E-1, E-1B and E-3 isn't to do with the buttons file - it's to do with how the E-1 was originally made by Ranwers. The E-1B and E-3 were based on the E-1 model, hence the shared problems.

I've narrowed down the faults and at the moment have the E-3 working perfectly (with a custom built proper early canopy too). I know the problem with the E-1 and I'm working on a fix at the moment.

Joe
Reply
#5

Joe,

Thanks for taking the time to look deeper into this little problem. It is quite annoying but clearly not impossible to work around. If you dont mind my asking, where exactly in the file structure do the conflicts occur and how?

Justin
Reply
#6

When I realised the problem existed with the 109E-1, I guessed that the E-3 was based on it and that the E-1/B and E-3B wouldn't work. I also found it odd that it would be the buttons file since not everybody has the problem.

I have no idea about code, etc but my brief investigations did lead me to suspect that the problem could very well be the way the aircraft were made.

Thanks for your insight Joe.
Reply


Forum Jump:


Users browsing this thread: 6 Guest(s)