|
|
Post by ftldave on Sept 13, 2012 4:49:33 GMT
Hi Everyone, This evening I set up the Boeing 707-320C with a Pan-Am texture on my FSX Acceleration (Gold Edition) sim with no problems. I've familiar with aliasing, the 707 shows up in my aircraft listing, and all is good. But FSX always crashes to the desktop when I attempt to start a flight with the 707, reporting that 707-320.GAU, one of the core gauges, is the offending object. I'm using the HJG B707-320B-ADVC 1965 panel, and it contains the disclaimer that the alternative fsx panel.cfg is not officially supported by HJG. Uh-oh.  My OS is Win7-32, and other than running a registered copy of FSUIPC, I had no other add-ons active during this session. The pc has 4GB of RAM, and always runs FSX well, no crashes even on the the longest flights. Any suggestions? Thanks heaps! FTLDave Bloomington, Indiana, USA |
|
|
|
Post by aerofoto - HJG Admin on Sept 13, 2012 5:57:25 GMT
When you fly the B707-320C ....
Are you going straight to that particular aircraft in order to start your FS session ?
OR ....
Are you loading the default MSFS CESSNA (or whatever it is in FSX) into FSX "FIRSTLY" .... and then proceeding to your B707-320C "SECONDLY" ?
I'm not FSX myself, but, I do recall commentary to the effect that, on some systems/FS installations, it may be necessary to select and load the/a default MSFS aircraft into FSX "FIRSTLY" .... and "THEN" change to/select, and load, your add-on aircraft of choice "SECONDLY".
Try doing that .... and see what happens !
Don't pay too much attention to this above line of text which appears within each of the B707 panel installation instructions documents. That data was compiled quite a while before we ever had an FSX SUPPORT forum here at HJG.
All of the the HJG B707/720 SERIES models, and panels, are portovers from FS2004 .... to FSX .... but .... so far as I'm aware they do work fine in FSX .... save for the panel side views (only) possibly not working/appearing within FSX.
All one must essentially remember to do in the case of FSX installation of these these particular aircraft files .... is to delete the default FS2004 AIRCRAFT.CFG (as well as the default PANEL.CFG and SOUND.CFG files too) and then activate the FSX versions of these files .... by simply deleting their _ (underscore) "FSX" suiffixes.
They do all otherwize work in FSX though regardless .... and we do know that for sure !!!!
Mark C
AKL/NZ
|
|
|
|
Post by Dan K. Hansen on Sept 13, 2012 8:03:12 GMT
Hmm. not that it is of any help to you of course .... but I've been running with this gau on FSX for about 6 years now without problem .... so I'm pretty sure that your issue is not in our gau alone, but perhaps some interaction between this and something else .... there could be any number of reasons.... but try out Mark' suggestion first and see how it goes....
Btw. be sure of course that you have our latest version of the gau installed. And be sure you run under administrative account too (I saw you were on win7)
|
|
|
|
Post by aerofoto - HJG Admin on Sept 13, 2012 8:35:47 GMT
And FYI ....
The current B707 panel gauge dates (last modified dates) should be as follows ....
707-120.gau = Saturday, 5 June 2010, 8:04:38 a.m.
707-320.GAU = Saturday, 5 June 2010, 8:52:58 p.m.
707-LATE.GAU = Saturday, 5 June 2010, 8:56:42 p.m.
If the gauge date you see doesn't correspond with these (as above) then redownload, and reinstall, the B707 PANEL GAUGES/CORE FILES package once again .... but .... do try selecting, and loading a default FSX aircraft type "FIRST AND FOREMOST" .... because I'm "pretty sure" I remember not doing this apparently being the cause of such an issue, for some folk, previously.
Mark C
AKL/NZ
|
|
|
|
Post by Falcon on Sept 13, 2012 16:24:50 GMT
Your are correct Mark. Not loading defualt MS aircraft first in FSX will result in many strange events. I have done this many times by mistake before I finally made a default A/C that loads first. I"ve never had a problem since with HJG's 707's.
Falcon
|
|
|
|
Post by ftldave on Sept 13, 2012 16:32:00 GMT
I verified the proper date stamps on the gauges and they are the correct versions. But I was going direct to the B707, not loading any default aircraft first. Will retest with the new procedure this evening.
|
|
|
|
Post by ftldave on Sept 14, 2012 1:51:19 GMT
No joy. Loading a default aircraft (Cessna or CRJ-700) first resulted in a new CTD error when I tried to fly the B707: BEX - buffer overflow exception. I tried turning off Data Execution Prevention (DEP), a common cure for BEX, but then FSX.EXE itself was identified as the crashing component on the following test. Next, tried a different panel, the B707 1970, but same results, alas. The aircraft loads up fine with Philippe Wallert's generic 707 2D panel. My rig just doesn't like the core 707-320.gau. Kind of surprising because, as I said, my FSX setup is pretty vanilla, only FSUIPC present. Squawkbox 4 is present but not running, but that's all. And I had turned off my Microsoft Security Essentials realtime virus protection during testing, too. Comparison to others who can run this okay aren't that relevant unless they're also on the same OS, Win7 32-bit version, like mine. It's the only time I've encountered this, having successfully installed and flown other payware and freeware packages. Philippe's panel isn't as rich as HJG's, but I can still enjoy the great B707 models. My thanks to all who responded with suggestions for a fix.
|
|
|
|
Post by aerofoto - HJG Admin on Sept 14, 2012 2:36:34 GMT
"STRANGE" .... considering the gauges set "IS" in-the-clear.
Different files can react differently on different PC's/OS's though.
Unfortunately I'm not sufficiently FSX conversent to advise/suggest further .... so .... must leave you/this query in the hands of those whom are.
Mark C
AKL/NZ
|
|
|
|
Post by Dan K. Hansen on Sept 14, 2012 8:00:48 GMT
Just a wild idea.... try scanning your FSX foler inclusive sub folders to check if you by accident should have two versions of the file...? other things: do you run windowed or Full screen? did you disable the UAC? Are you running FSX.exe as an Administrator? Please post the exact error message. Of course you are also using the FSX-version of the aircraft.cfg ... not only the panle.cfg? Which sounds do you use? You DID get the files from our site, right? not from flightsim, avsim or whereever ....?
|
|
|
|
Post by Dan K. Hansen on Sept 14, 2012 8:15:41 GMT
Skimming through this section of the forum I found a few others having the same issues as you with this particular gau... unfortunately many of the request ends in our response and suggestion, but the requester do not return, so we can't really see if any of our suggestions have actually worked in the past .... another thing you might consider is to take a back-up of your fsx.cfg file and let FSX rebuild you one upon restart...(you manual settings must be re-entered afterwards)
|
|
|
|
Post by ftldave on Sept 14, 2012 18:44:44 GMT
Dan, I'll try to answer your questions in order.
1. I assume you are referring to multiple copies of fsx.cfg. Unlikely, since I had added an HJG directory as a new SimObject and have installed the B707, HJG panels and sounds in it, and they show up fine.
2. I always run FSX in full screen.
3. UAC is disabled.
4. I am logged in with an admin account, but have not been running fsx.exe as an administrator. Had no need to, but I will test it in that mode.
5. I will post the error message in a follow-up message.
6. Yes, I am running the FSX version of aircraft.cfg and panel.cfg, renamed those files to replace the FS2004 defaults, per the installation instructions.
7. I'm trying to run the B707 with HJG panel and sound. As mentioned before, I was able to fly the B707 using an alternate 2D panel, but that was just for the test. All components are from HJG.
Will post a follow-up in about 10 hours. Duty calls.
FTLDave
|
|
|
|
Post by Dan K. Hansen on Sept 14, 2012 19:09:35 GMT
Ad 1.: no I was actually wondering if you might have multiple versions of the gau, laying around somewhere ....
|
|
|
|
Post by ftldave on Sept 15, 2012 17:13:13 GMT
Getting closer to a solution. First, running fsx.exe as administrator did not prevent the crash-to-desktop, no difference. Then I backed up my fsx.cfg, deleted it, and let FSX gen a new one. The HJG B707 flight deck loaded without error. What's the diff in my fsc.cfg? Not sure yet, and it will take some time debugging it. Last month I had used Jesus Bojote's FSX Tweak ( www.venetubo.com/fsx.html ) that modified fsx.cfg, and had gotten a nice performance boost as a result. But there's something in the settings that causes 707-320.gau to crash. I suspect it to be a buffers or graphics parameter. I'll try to pin it down with more testing. FYI: this is the CTD error message I'm getting now. BEX signifies Buffer Exception Overflow has occurred. Sometimes the error messages do indicate 707-320.gau as the fault module, probably depending on how fast FSX has crashed! Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 000000e8 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 |
|
|
|
Post by Dan K. Hansen on Sept 16, 2012 0:30:57 GMT
Well the Exception code: c0000005 is a memory access violation .... something is trying to write to a part of the memory which is already in use, the machine don't know which program to give first priority, and then gives up...
That's the easy explanation... the tricky stuff comes when trying to find out why ..... that's more difficult especially if you don't have hands-on access to the machine ... because what causes memory access violation on your machine/setup might not do the same on another.... And I would need to run the code in debug mode and try to replicate your particular scenario in order to re-create the error... so unfortunately it's not likely that it can be solved just like that...Your dump indicates that the faulting program is FSX.exe, but when you begin to load in all sorts of add-ons to your FS (which we all do) the most of them will run in the same process as the main application, and thus the error is indicated coming from this hence it is logging fsx.exe ... but actually it could come from anything running under the same process ....
|
|
|
|
Post by ftldave on Sept 22, 2012 20:35:48 GMT
After an intense line-by-line debugging session with FSX.CFG and lots of launching-closing-relaunching FSX, I discovered the difference between my normal FSX.CFG that CTDs when 707-320.gau is loaded and the generic FSX.CFG which runs 707-320.gau with no problems. The first configuration was launching in maximized window mode, the latter in full screen mode, a subtle difference I had not noticed during testing that turned out to be the critical factor. Starting FSX in or changing-on-the-fly to maximized window mode, with a panel invoking 707-320.gau, immediately causes CTD on my rig. That was the only major difference between the two FSX.CFG files.
Here are the 3 different FSX.CFG parameters that I tested:
[Main]
Maximized=2 //Maximized Window mode = CTD with aircraft using 707-320.gau - FAIL
[Main]
Maximized=1 //Full Screen mode - No CTD with aircraft using 707-320.gau - SUCCESS
[Main]
Maximized=0 //Resized Window mode - No CTD with aircraft using 707-320.gau - SUCCESS
Maybe it's specific to my pc and its innards: ATI Radeon HD 5670 video card, Catalyst 12.8 video driver, 4:3 monitor, 1280x1024 res in 32-bit color, 3.2 GHz Core 2 Duo cpu, 4 GB RAM, Windows 7-32 bit OS. It's a modest rig by today's standards, sure, but I get close to consistent 30 FPS in FSX. And, as I mentioned before, the one-and-only add-on cited in FSX.CFG is FSUIPC, not a likely suspect for my problem.
So, now I know what's required to run the HJG B707 panels and can enjoy them in my future flights!
|
|
