CTD when exiting FSX after flight

[WarHorse47]

Well, I don't know what to tell ya' guys.

Kevin had me run through 16 variations of the dll.xml and I created a couple myself. The only time I did not encounter a CTD upon exiting FSX was when the MILVIZPACK was removed from the file.

My sense is that my dll.xml is simple and straightforward as I do not have that many addons. So I'll be curious to see how this evolves.

Thanks

--WH

[Basti_793]

I think the problem is the memory management. The results speak for themselves.
But in C++, each section must be considered separately. That's very costly in time
and cash and the guys have my respect for that.

[ncooper]

Workaround (up to solve the problems)
1. Run the FSX not with an AN-2 as standard flight.
2. Load always a flight without AN-2.
3. Select then your AN-2 flight model.
4. Open not the logbook after an AN-2 flight.
5. Before opening the logbook, select a different flight model.
6. Exit the FSX not with an selected (activated) AN-2.

This is what I can do.

1. Start FSX with an AN-2 default flight.
2. Load a flight with AN-2.
3. N/A
4. I never use the logbook, is this the problem?
5. As 4.
6. Exit FSX with a selected AN-2.

I have never seen a CTD before, during or after a flight.
I respect your research but have never seen the problems.

Regards,
Nick.

[Basti_793]

Hi Nick,
each pc configuration (hardware etc.) is different. Even with a chipset series,
there are large tolerances. And that is the big problem for all software devs.
The wide range of different system reactions can't always be considered.

But Alex has already responded and optimizes the code.
More infos after the next tests in a few days.

[Basti_793]

Hi guys,
the CTDs are history, but during the test then came other unsightly things.
As I said before, the whole process of troubleshooting in the AN-2 Memory
management is probably a bit difficult.

However, I appreciate that Alex has taken this issue.

[iwn]

Sounds really good, its a pity keep this pearl unused.

[musterpilot]

Well everyone I have been tearing out my hair with this problem and I think I have solved it
go to your FSX cfg and in your
[MAIN] section if you have this entry "DisablePreLoad=1" get RID of it or change to "DisablePreLoad=0"
I went through my cfg and every time I put that in I got a CTD
took it out of my cfg and every thing was ok
Try it I hope it works for everyone else
I can now load my AN-2 as my default flight and exit without any problems
John

[Basti_793]

That sounds interesting and I can confirm that John.

Even if delete this tweak helps many users, it doesn't change the fact of an required revision of the memory management.

The switching between each menus after a flight (Free flight -> Logbook check -> Free flight for example) and the reloading of the AN-2 is nevertheless very unbalanced. The reason for this effect is still a problem in memory management of this flight model.

I hope that Alex & team will present a fix soon...

[iwn]

Disablepreload is one of the crucial FSX tweaks. It would be too much to ask to give it up.

[musterpilot]

Disablepreload is one of the crucial FSX tweaks. It would be too much to ask to give it up.

Well I think it is up to the developers to fix this problem please

[ncooper]

I disagree entirely.

The disablepreload "tweak" is just that, a tweak.
All it does is what it says, it disables the ability of FSX
to preload before the "Fly Now" command is selected.

One, I have never used it and never had a problem at all,
let alone a CTD on exit of FSX.

Two, it is well and truly outdated.

Three, one cannot expect a developer to modify
their product to suit every user's desire to mess
with FSX.

I would suggest altering =1 to =0, better still
just delete the line and put this "tweak" behind you.

Regards,
Nick.

[adi518]

I disagree Nick. You're circumventing the problem instead of fixing it. I put my trust in Alex. He will fix it.

[froggy]

I agree with Nick.
The disablepreload "TWEAK" had no effect on flight fluidity or FPS gain.
It was at the time for very slow PC & only help to save few seconds at FSX opening.
Pretty secondary tweak in fact.
If they could "fix it",if i could say , well but they shouldn't worry too much on that & putting (to not say wasting) precious time for a useless tweak.

Regards

André

[Basti_793]

Just as the swan2.dll is programmed up to now, it can't stay. The gap in memory
management must be closed. Urgently, whether with or without tweaked FSX.

[musterpilot]

I think I will have to retract my last comment and agree with you guys
I did not know that disablepreload was a addon to the cfg

John

[Alex]

Guys, first of all thank you for your help in this issue.
I've played with disablepreload in my test systems and still can't repeat this bug.
Could you send my your fsx.cfg (only if you have CTD)?

[ncooper]

As outlined in the posts above this one, the DisablePreload=1 line contributes nothing to FSX or its performance.
While it does hasten the appearance of the opening screen, FSX has to load the the scenery at some stage
and any tiny amount of time saved is used up waiting for the black line to rise above 6% after clicking the Fly Now button.

(As an aside, a far better "tweak" is to use the Scenery Config Editor to group and then select your scenery so that FSX has only to load the
scenery you intend to use for your flight and not for the entire planet. For anyone with a great deal of addon scenery,
this will save several minutes in loading time.)

I see from other developers' posts in other fora that yours is not the only model that may suffer ill effects from this "tweak".
I see also that you instruct users of this aircraft not to use Compatability mode and I wonder if it might be worth adding the advice not to use this "tweak".

I have no idea who invented it but I do believe that it has never been part of the default fsx.cfg file.

Regards,
Nick.

[froggy]

I have no idea who invented it but I do believe that it has never been part of the default fsx.cfg file.

you're right,it has never been part of any fsx versions; RTM,Deluxe,SP1,SP2,Acceleration or Gold edition.

The DisablePreload=1 TWEAK prevent to load, not a saved flight in your docs located at:
C:\Users\user\Documents\Flight Simulator X Files, but It prevent to load a special flight located inside the main FSX folder located at:
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Flights\other\FLTSIM.FLT.

Maybe i am wrong, but as i see it the AN-2 seems to have coding who need the default values of this flight to work from.
If its the case, its not a bug.

Regards

André

[iwn]

I think Basti has pointed out quite exclusively that this is a far deeper problem than some fsx tweaks. I don't keep this addon installed until a cure is found. It certainly does not help to maintain a stable sim if it crashes everytime it is shut down.

[iwn]

I changed DisablePreload to 0 and the experience was most discomforting. I had to wait ages for choosing scenery and aircraft, they just kept loading. So, no thanks. Got to be another way.