|
Post by Dan K. Hansen on Jan 20, 2008 22:43:18 GMT
I use FSX:A which includes SP1+SP2 (as mentioned in the "Known Issues" thread)
But alas, I've seen these random crashes in FS9 pre- and post sp1 as well in FSX before and after both SP1 and SP2 ....
But still: It is only a few that have reported this, and I must repeat: It is a random error, and thus very hard to catch.
|
|
luke
CV-990
Posts: 36
|
Post by luke on Jan 21, 2008 19:14:15 GMT
But still: It is only a few that have reported this, and I must repeat: It is a random error, and thus very hard to catch. Then I have something different - my panel just refuses to load at all. Cheers! Luke
|
|
|
Post by Dan K. Hansen on Jan 21, 2008 19:23:40 GMT
That sounds very much like a failure in the install procedure.... Please go through the guide available in this thread, and be sure to follow every step closely (look especially to point 9 in your case). You should have no problems at all: Here
|
|
|
Post by carl246 on Jan 22, 2008 18:01:05 GMT
I'm using SP1 - I'm going to wait a bit for SP2
I downloaded BOAC B707-420 with it's panel and get the same problem.
These aircraft (720 & 707) work great if I select a new aircraft once in flight.
Carl
|
|
|
Post by Dan K. Hansen on Jan 22, 2008 21:08:13 GMT
I wouldn't wait with SP2, but of course each to his own. SP2 really solves a lot of especially performance issues as well as some texture issues with dark flight deck windows etc. etc.
The CTD is a random issue and to the very best of my knowledge, not related to either FS9, FSX with or without SP's.
I've had them in FS9 as well in FSX but as of lately I haven't had any....
|
|
|
Post by carl246 on Jan 25, 2008 10:52:39 GMT
Hello, see my feedback under pollb707/720 crashes in FSX
Carl
|
|
|
Post by kittx1 on Feb 4, 2008 2:49:30 GMT
Hello,
Just wanted to let you know that I've since reinstalled a fresh copy of Windows XP SP2 and Flight Simulator X SP2 since I started this thread, and I'm having the same problem again. As suggested on this thread, I removed the "window00" line from the panel.cfg file and now my panel works again.
However there are a few glitches, such as some of the panels do not appear when I click on the panel button, and instead I just see an outside shot (at the angle where the panel should be), and also the rightmost gauges do not seem to move (such as flaps). Any suggestions? Should I now renumber all the panels starting from 00 now that I removed the introduction panel from the cfg file?
Thanks.
|
|
|
Post by aerofoto - HJG Admin on Feb 4, 2008 5:19:38 GMT
"KITTX1" .... if you're going to mess around with PANEL.CFG files then I caution you (everyone) to be careful what you deleting or modifying .... or .... you're going to potentially create "PROBLEMS" for yourself NOT A VERY GOOD IDEA ! "IF" .... you remove "WINDOW" entries from any PANEL.CFG then that's likely going to be the cause of some panel views then not working when go go to select them from panel selection tabs .... or .... it'll cause other things to fail. Personally .... I wouldn't encourage modifying any of that PANEL.CFG data at all. Instead .... I'd simply delete what you have and reinstall the whole panel again. I realise this's not likely to resolve you CTD problems, but, I must stress, it seems only "some" (most certainly not all) folk are experiencing these problems in either FSX or FS9. "IF" .... this issue comes down to "VARIABLES" between different computers (PC's are often unalike and don't necessarily perform the same) then I regret to say it's likely going to be extremly difficult to try'n identify the precise cause of these CTD's. Not news you want to recieve .... and not news I want to announce either .... but .... I must be quite frank here folks ! These CTD's most certainly aren't a universal problem. Mark C AKL/NZ
|
|
|
Post by Dan K. Hansen on Feb 4, 2008 8:00:44 GMT
There have been no advice of removing the [window00] section.
See under the 'Known Issues' thread.
What has been suggested is to comment out some of the individual lines under the section. Removing the section completely gives you the problems you describe.
This is also mentioned in the suggestion, so if you are about to mess with the config files your self, then please do your self a favour of reading the suggestion thoroughly... including the part as Mark has pointed out, with no support on doing it.
|
|