Milviz F15E strike eagle CTD's

[Captain Vodka]

After spending a couple of week now on the Milviz F15E, much with some trials and tribulations..

 

Thought I’d give some pointers for anyone thinking of getting this ship’

 

OK firstly you have to have Acceleration installed or you will lose functionality of some of the aircraft major elements. Afterburner for a start. No acceleration pack, no afterburner whatsoever. Without the AB you’ll be bleeding speed as soon as you lift off. It’s a must!

 

Secondly I had endless issues with CTD’s with this piece of software. I was almost at the point of giving up on it and binning it out of my hangar. The issues were once installed I would get one flight and ‘hopefully’ land. After the flight id go back to the main screen and set up another flight. That’s where the troubles occur. Once you hit ‘fly’ your taken to the loading screen as per normal, you get to 100% load and . . . sound of inside the cockpit and. . Blank screen. .then CTD every time!

 

This was somewhat demoralisin. I looked at the milviz forum to see if there were any tips. There were quite a few reported CTDs but nothing really in depth to the point of the ctd , where / when or a work round / solution. Was a little ‘grin and bear’ it to try and work something out. Seemingly lots of happy customers so something had to be wrong somewhere on my rig perhaps?

 

Firstly this is the only aircraft I have any issue with whatsoever. I have carenado, A2A, Ants planes, Dino’s all 100% on the money. I even have milviz F86A. All fine and dandy as we say. It was just the F15E that was CTD every time after that first flight. I uninstalled, reinstalled at least a dozen times, just so I could at least get one flight. .yes I know. .how ridiculous was that. It’s just when you get a flight loaded you will see why I troubled myself to persevere here. It’s a real beaut’ of a ship to fly!. . And hopefully land.

 

 

So first let’s look at my rig to see if that was an issue

 

Wn7pro, Intel i7 overclocked from 3.8-4.2ghz. 32mb RAM, 2Gb ATI ice Q 6950. FSX +acceleration running standalone on SSD256gb. Thrustmaster F16 Hotas, Saitek panels, autopilot, radio/ nav plus switching panel. TM MFD’s. All latest drivers installed to date inc FSUPIC..and EZdok. So now slouch in the pc rig whatsoever. Tweaked cfg nicely running smooth. ALL ok on everything else. Running two screens. One Samsung and one LG but they have different resolution. The main Samsung is 1680 x 1050 60hz. And the LG 1280 x 1024 60hz. I thought perhaps there is an issue with a conflict in the different screen resolutions. I run extended screen mode by the way. Main screen with cockpit window and the LG smaller screen with perhaps gps running or another instrument. But, as I say, no problem with anything else flying and causing problems

 

So I thought I’d try something. Perhaps start and run a flight in window mode and not full screen?

Reinstalled the F15E, ensured I would start in window mode by loading up another aircraft first and exited out of FSx in window mode. Booted fsx back up. Loaded the f15E up and. .

 

Shazaaam! Works. Straight into cockpit and no ctd.

 

Ran a few more reloads, either in window mode all full screen mode and same thing every time.

 

If in full screen mode. First flight after reinstall would work then CTD every time. Reinstall; start each time in window mode and Alt-Ent once in cockpit to full screen. Take Off, land. Then at shutdown go back into window mode. Exit flight set new flight up and back in window mode in the cockpit. .no CTD whatsoever.

 

Conclusion

 

Clearly there is an issue here with the Milviz F15E starting any flight after its install and then its first flight but starting and finishing in window mode solves the issue.

 

I cannot say if this is a generic issue overall or just something with my system / install but it is the ONLY aircraft that CTDS and requires this method of running successfully.

 

On the Milvzs forum there are a few ‘odd comments’ from the milviz admin team in regard to other issues people have raised. Some of the replies are a little ‘not our fault , not our problem’ on occasion. That’s not to be derogatory in anyway , just an opinion.

 

Yes we know Win7 has some memory leaks as does every other OS out there but let’s not just blame memory leaks or ‘floods’ as some might suggest are always the problem.

 

So , nice ship to fly once you have a work round of the CTD’ or at least in my situation here.

 

Hopefully this is helpful to others.