|
|
Post by emmemm on Sept 15, 2021 11:53:41 GMT -5
Hallo classic FS9 fans,
i have a big problem with my "modern" FS9.
The FS starts normally with the start situation. But when I do something, like opening doors or starting an engine, all textures go away. First the textures of your own aircraft, then gradually those of the AI planes, the default buildings, the add-on scenery and so on. In this situation, I can't choose another plane, the screen goes black and I can't even call up the task manager, just log off the computer.
If I immediately after the problem occurs the FS with Contr.-C turn off, I come back to the desktop, but the task manager shows me that the FS is still running in the background!
The FS9 ran for a long time under Windows 10 without any problems and now this. It is strange that my classic FS9 on the same drive is not affected and works normally.
Can someone help me here? I ask here because some old FS9 dinosaurs like me are still active in this forum.
Manfred
|
|
|
|
Post by Tom/CalClassic on Sept 15, 2021 13:13:23 GMT -5
Wow, that's an odd one. Are you running any compatibility settings that may be different between the modern and classic versions?
|
|
|
|
Post by emmemm on Sept 15, 2021 15:56:50 GMT -5
No, both ran without compatibility settings or problems so far
|
|
|
|
Post by zswobbie1 on Sept 16, 2021 5:01:06 GMT -5
Very odd.. My usual 'go to' thing to do is to delete the fs9.cfg (back up first)
When you restart the sim, a new cfg will be created.
Maybe that will work?
|
|
|
|
Post by emmemm on Sept 18, 2021 11:19:57 GMT -5
I also tested it with a new, fresh fs9.cfg or with a new fs9.exe the simulator shows the same behavior and is unusable. The second "classic" fs9 on the same drive works fine. But also with the exe and the cfg of this simulator the "modern" fs9 shows the wrong behavior. I'm desperate. The FS contains 262 GB, 1100 entries in the scenery library, payware and freeware around the world. It is impossible to make everything new.
Manfred
|
|
|
|
Post by connieguy on Sept 18, 2021 12:09:00 GMT -5
Manfred,
The logical solution would be that you have done something with the modern version that you haven't done with the classic and that would seem quite likely to be adding something new. Faulty scenery can cause crashes, but I have never heard of what you are describing. You can always copy your 262gb of scenery to an external hard drive to preserve it so that it can be reinstalled in a new version, providing of course that it doesn't contain what is causing the problem. Have you tried unchecking every item in the scenery library and seeing whether it runs properly then?
|
|
|
|
Post by emmemm on Sept 18, 2021 13:55:20 GMT -5
unfortunately it's not that easy. I got the bug on 09/13. discovered and I am firmly convinced that I had operated the FS normally the week before. I haven't installed any scenery or aircraft in the meantime.
Incidentally, today I installed an FS9 fresh out of the box on my notebook / Windows 10), which runs immediately without any compatibility problems.
MM
|
|
|
|
Post by JasonK..AKA "Pal Joey." on Sept 18, 2021 14:44:36 GMT -5
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 19, 2021 14:33:08 GMT -5
Could you eventually consider to run modern and classic FS with one and the same installation? I run different eras while just renaming the scenery configuration files. It means 'scenery_ x.cfg' or 'scenery_y.cfg' in 'scenery.cfg', depending in which world I would like to fly. For better handling I manage two aircraft folders, one with classic and the other with vintage planes. I just rename these folders as well, but mostly I use the first one.
it sounds a bit complicated, but it isn't. Running my FS versions this way, I'm able to use all the same tools like IS, AFX and so on. FS9.cfg remains allways unchanged. In any case, only one version can be run at a time!
Please understand this advice only as a possible and at least temporary solution.
|
|
|
|
Post by emmemm on Oct 11, 2021 10:47:59 GMT -5
Hi,
many thanks for the answers and hints.
Unfortunately, despite many hours of testing and attempts, I was unable to find the error.
Fortunately, I still had a copy of my "modern" FS9 a little over a year old on an external hard drive. I am now using this well-functioning one and will gradually bring it up to date, at least until the error occurs again.
Manfred
|
|
