FSDreamTeam forum
General Category => Unofficial F/A-18 Acceleration Pack board => Topic started by: Liftow on November 05, 2007, 09:52:26 pm
-
Hello, I'm unsure if I'll get any support for this issue here, but I thought that I would try....first of all, great job on the FA/18 - really fantastic....however, some issues have arisen with CTD's specifically while using functions on the F/A-18 Panel...these are easily replicated and constant within my sysconfig - and others are reporting them as well....first, while using the direct to function on the gps while in the F/A-18, after selecting a destination and hitting the enter key it would result in a CTD everytime...i've fixed this error by uninstalling FSX Accel. and repairing the original FSX install, then copying the two gps cabs from the gauges folder and reinstalling Accel and overwriting the new ones. This has fixed the gps direct to issue....Secondly, now when flying a flight plan or direct to plan - after hitting the seq key on the panel to fly the route, a CTD occurs everytime...again these are constant and easily replicated...
This forum documents others having this issue http://www.flightsimworld.com/forums/index.php?showtopic=130066
I believe that there is also a thread over at Avsim about it...while I realize that you probably don't offer support for Microsoft products, I was hoping you may have some insight or advice for us?
Thanks very much for your work and help
-
The only thing that I can say, it's that I never been able to replicate this problem. Yes, I have seen some users reporting it, and now that I read you messsage, maybe I have some ideas.
The F/A-18 navigation is not supposed to be used together with the default FSX GPS, I never tested it in such environment. The F/A-18 gauge calls into the FSX gps.dll directly, as the FSX gps gauges do. I don't know what might happen if you use both at the same time, because this is not how one is supposed to use it. The usual workflow is to use only the FSX Flight Planner, and then interact with the flight plan with the regular F/A-18 avionics only, without using the gps gauge at all. I'd even get rid of it in the panel.cfg, just to be sure...
-
Thanks for the response virtuali...that would make sense and now I can stop pulling my hair out trying to figure out what was wrong...I'll pass on the information to others and perhaps we can find a way to get the two working in unison....
Cheers!
-
I have the same problem here.
When I dicovered the forum, I decided to follow the Flight Planning Tutorial.
Flight plan done, load flight and then SEQ key pressed... CTD!!!!
The only way to make things happen is to load a free flight, then, through the menu, I load the flight plan saved before. Back to the VC, now I can press SEQ key...
If I save a flight while flying, if I press the SEQ key after I load it back, CTD again!!!
-
I too have this problem. For me it seems like every other launch of the game gets a ctd. When I go back in the seq works and it doesn't matter how often I click on it while on a mission.
-
No CTD's here ! I have loaded plans via the default planner and used only the cockpit avionics while flying.
Vista 32, FSX, Acceleration, Xload, UTX USA & Canada
AMD 64 X2 6000+
Asus M2N32-SLI Deluxe
4GB 800mhz DDR2
XFX Geforce 7950GX2
SoundBlaster Xfi-Platinum
SATA 300 GB/s HD
Saitek X52
-
Hi,
Yep... same problem
Create plan/ send plane to airfield, in cockpit select WPT... select SEQ and it all falls over ???
Seriously, great work on the model :o
-
Sorry, still doesn't happen here. When I wrote the tutorial, I obviously had to take the same steps, load a flightplan, send the airplane to the departing airfield, pressing WPT and then SEQ to take screenshots, but I never had any crash.
Have you tried updating your Visual C++ runtimes to last version ?
You can do it by installing our Zurich scenery trial OR, if you are not interested, you can download the runtimes from here:
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
-
Nope... still no go
Problem Event Name: BEX
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.762
Fault Module Timestamp: 45712238
Exception Offset: 00008a8c
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 3081
Additional Information 1: 8988
Additional Information 2: 37aebcfc1ce546039b15a08dfa1a99be
Additional Information 3: 0be6
Additional Information 4: 38f4e2f248c4a825876a4e843322cbcd
-
This is strange.
Searching in Google for msvcr80.dll and the 00008a8c offset, gives several result, coming from all applications.
I used the name of the dll and the offset, because it gives an idea during in which function the crash happened. Msvcr80.dll is part of the VC++ runtimes, and the 00008a8c is an offset to one of the many library function. It looks like several other programs that do not have anything to do with Flight sim, also suffer from a crash in the same library function.
There's seems to be a pattern, some of the users fixed the problem by returning the memory management strategy to the default setting. Have you changed the swap file setting, from handled by Windows (default) to a specific minimum/maximum size ?
-
You da man!
I was running my Page File as Custom Size and your advice has given SEQ functionality, setting the PF back to System Managed.
I was running Vista 4 x disc RAID with a small (512MB) PF on the system and a larger (2048) PF on a seperate IDE disc
-
I had a similar problem, although when I originally installed Acceleration the F18 worked just as you described using the WP and SEQ keys for several weeks.
Until last weekend. I was starting a flight and went to the left MFD to set ACL for the autopilot page and got a CTD with the error pointing to the MSVCR80.dll module. I tried repeatedly after rebooting the system with the same result. All the other keys of the left MFD were fine and operated as you described. Then I tried the right MFD - pushed WP with no problem but when I touched SEQ CTD with MSVCR80.dll as the offending module again.
Scouring the forums and trying unsuccessfully different suggestions for most of the weekend I ran across someone noticing that if the 'light bloom' option on the graphics setting was activiated it would magically allow the SEQ button to operate properly. Normally I don't have that option running so I tried it, and it worked! Even better, when I reverted to disabling 'light bloom' it continues to work. So another odd piece to the puzzle!
This is starting to get discouraging, what a confusing hobby I've picked (20 years ago)! When it works I couldn't be happier, when it doesn't well its a frustrating pile of monkey dung.
Oh, excellent cockpit by the way!! ;D
-
Guess i'll join in too and share my experiences with the fa18 hornet. Tonight I downloaded the Zurich trial scenery with the latest runtime files and then started fsx just to see what would happen. At first attempt I loaded a flight plan and then took the plane to the runway..wpt..seq and the thing worked for the first time in several days. Just out of curiousity, I then went to the multiplayer screen and did the same thing and the program crashed to the desktop like it always does. Wish I knew how to fix this problem because the fa18 is a nice piece of work ,and i suspect you couldn't get any better unless you had pay ware.
-
Right now, the only fix that seems to work for many users, is to use the default Windows swap file management. Meaning, you should let Windows manage the swap file automatically, instead that specifically setting a minimum/maximum size.
Zurich shouldn't be affect the f/a-18, except for the fact its installer will update C++ runtimes to their latest version.
-
Well that doesn't seem to work for me either. The swap file settings have never been changed on this machine. I did find that the WP and Seq keys have never worked in multiplayer for me. They sometimes work after filing a flight plan in free flight but only after i'm in the cockpit and on the runway. Thinking about uninstalling it and doing a reinstallation to see if that helps.Hopefully someone at fsdreamteam can come up with a solution for this. I realize this is the fa18 board but was wondering if a manual would be available for the other air craft in the Acceleration pack as well.
-
I don't have a solution, other that having it confirmed (as you can see from other user's messages) that with Windows swap file set to automatic, they solved the issue.
I'm still unable to reproduce it, BTW.
-
Greetings,
Love the F18 you did however I am also getting consistent CTD's when using the SEQ button and the ACL button on the MFD's.
I checked my swap drive settings, have the latest video drivers, downloaded and installed the VB Runtime library.
I am running on Vista Ultimate 32bit.
Would love to get these functions working.
Thanks
-
Sorry, I can't offer you any help, rather than saying that other users solved the issue by using automatic swap file settings. I can't reproduce this issue and never had any crash, with Vista 32 bit.
The updated runtimes are for Visual C++ SP1, NOT VB!
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
It might be useful to try updating Visual C++ Non-SP1 version as well:
http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en
Note the last message of this forum:
http://www.flightsimworld.com/forums/index.php?showtopic=130066&st=0&p=1613062&#entry1613062
another user that apparentely solved the issue by updating C++ runtimes. It's important to note (as the poster suggested) that, since both downloads have the same name, you download and apply updates one at a time.
-
My apologies but it was the Visual C++ runtime that I updated based on a earlier post. I made a mistake in saying it was VB.
I have since updated both versions as stated in your post above. Still no luck.
Here is the event msg from the crash.
Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module MSVCR80.dll, version 8.0.50727.1433, time stamp 0x471eb5ae, exception code 0xc000000d, fault offset 0x00008aa0, process id 0x1428, application start time 0x01c84d8452c7fd0b.
Also note that on same PC booted into XP Pro w/ SP2 I do not get the CTD.
I guess I'm stuck playing the game in XP, until a fix develops.
Thanks for your time.
-
I also am experiencing that problem described here with the SEQ button. I run XP SP2.
If the way points are created in the plight planer as described in the guide, it works ok but if its done from within the cockpit once F/A-18 is on the air, it always crashes.
[attachment deleted by admin]
-
SEQ button is killing me... nothing seems to fix this problem, it will always crash, no matter what, when i click the button and i have a flight plan
-
its getting worse
when i have a flight plan, i click the WPL button and then i get a CTD if i click any other button on mdf after the wpl....
windows xp 32bit sp2
-
Sorry, but I can only confirm I can't reproduce the problem, and several users confirmed they fixed the issue by returning to Windows default swap file settings. I'm using Vista, though.
The crash happens in one of the VC++ runtimes (MSVCR80.DLL), I keep seeing users with different versions, perhaps it's related to a specific version, or a bug introduced (or fixed) starting from a release onward.
I don't think it's specifically related to OS used. One user says he doesn't have the issue in XP, you have XP and have the issue, I have Vista and don't have it. It's probably more relaated to the specific local config of Windows sytem files and settings.
Another solution worth investigating might be removing the default GPS from the F/A-18 panel.cfg. Since the F/A-18 calls into the FSX GPS functions, it might be they can't work together at the same time.
-
nothing seems to work, i downloaded the latest version of msvcr80 and changed all my old ones, also removed the gps from panel.cfg, still having problems
i dont know why, but now i cant click the ACL button anymore or i'll get another CTD, and how do i remove a flight plan? when i click clear, the OK button becomes unclickable... im stuck with that flight plan that keeps me from clicking seq and acl now
EDIT: ok, this is really weird, i changed my flight plan, from the tutorial fp to a VFR / Direct -GPS with the auto generated route, and now both ACL and SEQ buttons are working.... lol
-
after testing this for a while, none of the above posted fixes seem to work. im still having this problem, but i can get the seq button working tho. thats what i do:
on fsx free flight screen, i open flight planner, create my own flight plan and save it, then i click fly now.
if i start the flight with the current flight plan, seq button won't work, and i'll get a ctd. but it works if i reload the flight plan when im already on free flight.
someone else having this problem test it and tell me if it works please.
thanks
-
It always works for me when I create a flight plan before I my flight. No need to reloaded once in the cockpit. The only times when it does not work is when I do NOT create a flight plan at all. Have yet to try to create plan after sitting in the cockpit. I'll try it and post results.
-
Virtuali,
If an Aircraft/Flight Plan is saved then:
If Free Flight > Load... > "Select Flight" > FLY NOW! then:
GPS screen will be blank (no waypoints). However when selecting WPT in the DDI the Waypoint Bearing Pointer appears along with waypoint info in upper right of DDI and in HUD (waypoint info from the flight plan that was saved with the flight).
if SEQ is selected CTD WILL OCCUR.
If Freeflight > Flight Planner (then Flight Plan is loaded or created from this screen) > Free Flight (select aircraft etc...) > FLY NOW!
CTD WILL NOT OCCUR after SEQ select.
So the difference is how the "Flight" itself is loaded (from Free Flight > Load... = crash)
Also the tip to preventing CTD is...
Before selecting WPT (certainly before selecting SEQ) select GPS in the DDI and verify that there are Waypoints listed. If yes you're good to go.
If not > display toolbar > Flights > Flight Planner... > Select Flight Plan (why you have to "resave" the flight plan after clicking OK is beyond me) and then this "should" cause the actual Waypoints to be displayed in the DDI.
At least this is what I "stumbled" upon and I hope it "resolves" the issue.
Rob O.
-
Rob,
thank you for giving a precise repro case. Now I've finally realized what's going on:
The HSI relies on a Simconnect notification event that is fired up when a flight plan is loaded, to update its waypoints list from the internal gps (The F/A-18 uses the FSX default GPS engine).
Unfortunately, it looks like Simconnect notifies the program that a flight plan has been loaded only when the *user* manually load it, not when the flight plan is automatically loaded together with a flight, that is the case if the flight was saved with a flight plan active.
So, without that notification, the F/A-18 gauges lose its synchronization between the gps flight plan and its internal data list, and that creates a crash.
The workaround for this is:
- As a general rule, do not save a flight when a flight plan is active. Load the flight, then load the flight plane afterwards when the airplane is ready to fly.
- If you already have flights saved with a flight plan active, before pushing the SEQ button, load the same flight plan again from the flight planner menu. This will trigger the flight plan loaded notification correctly, and the SEQ button will now work.