707 Panel crashes FSX session

[kittx1]

Hello,

I've been enjoying the 707-320B/C models with the b707-320badvc_panel1965 panel for a good month now. But upon having to reinstall FSX, the panels now crash when I switch to 2D mode in Full Screen (they work fine in windowed mode).

I know you are aware of this issue, but I wanted to chime in and let you know that there's at least someone else now having this problem, and that it DID work fine before on my system. I had to reinstall due to an activation problem when I upgraded my CPU. After 3 days of frustrating installation issues, I finally got FSX working again, but now the panel causes the problem you've mentioned.

The only feature I turned on after I upgraded my CPU was turning on 'Light Bloom' in the Display controls. While this affected some external views on the HJG models in foggy weather (it made the screen all white when using FS2004 models), turning it off did not fix the panel crashes I'm having now. A fix to this problem would be much appreciated, as I find myself fancying the 707 much more than the more modern 747, 737 and default A321 that comes with FSX.

They are truly beautiful models, and I honestly do not get tired of switching to the spot views in flight to gaze at them. Anyway, I eagerly await a fix to this annoying issue. Cheers.

[aerofoto - HJG Admin]

OK .... if these panels worked fine for you before then the fact they're crashing now is likely in relation to something that's changed as the result of your reinstallation .... though I couldn't hazard a guess as to what.

Our FSX representative is likely away until the New Year .... if you can bear with us until then.

In the meantime .... you might like to confirm the B707 CORE FILES package you're reinstalling is our latest version .... supported by "NOVEMBER 2007" dated installation instructions and not an earlier version ?

Are you using FSUIPC or not ?

What else have you got running in the background in FS ?

When you run FS do you quit ANTI-VIRUS and FIREWALL programs or not ?

A few folk (and I mean very few considering the enormous number of downloads these panels and gauges have witnessed) did report FS2004 crashes .... but not yet with these latest CORE FILES. The only way I could generate any crash at all was by making repeated aircraft/panel changes with the same FS session .... or changing between aircraft types too frequently without first going through the the default CESSNA or other default MSFS aircraft .... as covered per my B707 PANEL INSTALLATION & HANDLING notes on the "ABOUT HJG AIRCRAFT" forum page.

Mark C
AKL/NZ

[Dan K. Hansen]

Yes it is a known issue, and mostly observed under the circumstances Mark describes.

Also when switching between Full Screen and windowed mode, this can occur.

If you keep either in Full Screen OR in Windowed mode, it is not likely to happen. And don't switch to much between model-types. If you want to fly another type, the safest is to close FSX completely and start a new session.

Switching between different repaints of the same aircraft doesn't seem to have the same effect.

Now excuse me I must get back to the holidays ;-) See you all after new year.

[Tarasdad]

Try disabling in-game anti-aliasing. That solved most of my crash issues in FSX w/ HJG 707 aircraft.

[kittx1]

aerofoto said:

...you might like to confirm the B707 CORE FILES package you're reinstalling is our latest version .... supported by "NOVEMBER 2007" dated installation instructions and not an earlier version ?

Are you using FSUIPC or not ?

What else have you got running in the background in FS ?

When you run FS do you quit ANTI-VIRUS and FIREWALL programs or not ?

Hi,

The first thing I checked was for updated core files, which I did install (November 2007), but the problem persisted. I don't have FSUIPC and disabling Anti-Virus/ Firewall programs has no effect on the problem. I don't have very many programs in the background (something that hasn't changed since the first installation). Anti-aliasing is turned off. This occurs with all four textures I have for the HJG Boeing 707-320B-ADVC v6 and HJG Boeing 707-320C V6 planes.

Cheers.

[kittx1]

Update:

I deleted the .gau files from the gauges folder, and now the panels DO load when I switch to 2D flight deck (of course now I have no gauges). So the problem seems to be with loading the .gau files. Hope this helps.

[aerofoto - HJG Admin]

Thanks for responding with regard to those queries I raised further above.

At least those possibilities may be ruled out.

So the problem seems to be with loading the .gau files.

Possibly also .... it could just be the way these run with your particular PC as this experience appears by no means to be widespread.

I'm not dismissing your claim .... by any means, but, it does need to be borne in mind that different products will produce different results on different PC's of different configurations.

This where we may be getting into that complex and difficult realm of "VARIABILITIES" (as hinted within my "B707 Panel Installation & Handling Notes") .... more so if everything ran fine prior your recent upgrade as you see to indicate it did per your original posting.

Mark C
AKL/NZ

[carl246]

Hello

I'd like to thank you all at HJG for producing such great historical aircraft. I'm using the Air Canada DC8's and they work great with the latest updates.

My wife was/is a Bee Gees fan and when I saw the Bee Gees 720 I decided to download it.

Once installed, I too had an FSX crash with a 720 (707 files used) aircraft. I downloaded the Bee Gees aircraft including the core files, panel, gauges, manuals and sound. Upon firing up FSX with this aircraft, FSX crashed. I tried a few things and I found the culprit as being this file: 707-120.GAU I removed this file and everything worked fine (except no gauges working).

Hope this helps.

PS I'm using Windows Vista and FSX.

Carl.

[George Carty - HJG]

If my 707 panels crash your FSX setup, try disabling the windscreen wiper.

Comment out the line which includes 707-120!wiper (or 707-320!wiper or 707-LATE!wiper) by putting a semicolon before it, and change the render_3d_window=1 line before it to render_3d_window=0

[carl246]

George, tried your suggestion, it didn't work unfortunately.

I found that if I start FSX and load another aircraft type, on start up, I can switch aircraft(ie: to the 720) it works fine.

any other suggestions.

thanks,

carl

[Dan K. Hansen]

Hello Carl, and welcome to the forum

Not argue with George, but I believe you should do a double slash: // to comment out lines...

Carl you shouldn't remove the 707_120.gau as this is a vital gauge as you have seen (it contains mostly all the gauge you need in the panel, so disabling this is not an option...

I trust you have accepted the warning when FSX load the gau first time? If not you wouldn't be able to run the aircraft....

You are saying you are using Vista, and as I said, Vista has some security issues that I unfortunately haven't got the means to test, as I run XP....

Could you by any chance look into the eventlog, both application, system and security to see if there are any indication in there?

Unfortunately this is an issue that turns up every once in a while..... and up until know we haven't found the exact reason.... But please provide us with all the evidence/findings you can possibly get, as any clue might be the one that lead to solving the problem.

[carl246]

Dan,

of course I did not permanently remove the 707_120.GAU file, it was just for troubleshouting purposes.

Yes I did accept the warning about the gauges (ref. windows true blue) when loading a new aircaft for the first time.

I don't believe this is a windows security issue.

The event logs did not help. I did a bit more work. I temporarely removed the "Introduction Panel" and it's related list lines from the panel.cfg (yes the FSX one) I was able to fire up the 720 and get it flying with no problems. This may be the issue!

I'll keep testing it and let you know if I find anything else

Once agin, these are great aircraft and panels.

Carl.

[Dan K. Hansen]

Thank you for this input, and forgive me for asking silly questions.

We will take this into consideration as well.

[Dan K. Hansen]

We are try to figure out what can possible be causing this.

The problem is that is seems to appear on random, and that is the worst kind... to be able to correct it, the developer of course has to be able to recreate the error on purpose....

[luke]

I just got bit by this myself. Out of curiosity, do you and/or George have FSX SP2? They seemed to work just fine with SP1.

Cheers!

Luke