Sign in to follow this  
vonmar

fatal errors

Recommended Posts

I am testing v6.49 for the first time yesterday and today with Active Sky Next on a workstation PC.

 

All is good initially.

 

 

In FSX I get a fatal error just after lift off (did two test flights re-booted pc between flights same error) ... heading for my first waypoint.

 

In P3D v2.4 I got the fatal error during taxi on first and only test flight.

 

Anybody else seeing fatal errors?

 

Wonder if the Beta testers have ever seen this happen?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I used to get fatal errors with addon AI traffic (traffic x), it was something to do with some of the military AI (sonic boom or something like that) I modified the file after a google, and it fixed it. Can't remember the mod, give it a google if you have AI traffic addons ?

Share this post


Link to post
Share on other sites

Sonic boom may be your issue in FSX, keep an eye on which AI traffic Vox spawns for you. If vox spawns a military aircraft, you could expect a fatal error a short time afterwards if not immediately ? Sorry can't help with P3D though ?

Share this post


Link to post
Share on other sites



FSX Voxatc v6.49 / FSX fatal error departing KDTW for a flight to KCLE (screenshot sequence is in this short video).






P3D v2.4  Voxatc v6.49 fatal error while taxiing out for a KDTW departure to KCLE.

VOXatc-p3d-error-1_zps31d780da.jpg


 

Share this post


Link to post
Share on other sites

I used to get fatal errors with addon AI traffic (traffic x), it was something to do with some of the military AI (sonic boom or something like that) I modified the file after a google, and it fixed it. Can't remember the mod, give it a google if you have AI traffic addons ?

THANK YOU. I removed all military and GA from my Sim Object folder not just the scenery files and haven't had one since. I was having Fatal Errors at FSdreamteam LSZH right after "Line up" instructions or after take off and now no more. Which I think solved it for me. There are still weird AI behavior at certain addon airports but they never cause fatal errors.

Share this post


Link to post
Share on other sites

"I used to get fatal errors with addon AI traffic (traffic x)"

 

 Is this (traffic x) a purchased product from Just Flight?

 Did you have the errors in all previous versions and current version 6.49 of VOXatc?

 did you have errors in FSX and P3D V2.4?

 

 

 

"I removed all military and GA from my Sim Object folder not just the scenery files and haven't had one since. I was having Fatal Errors at FSdreamteam LSZH right after "Line up" instructions or after take off and now no more."

 


 And, my VOXatc errors are in FSX and P3D .. my P3D only has default AI (no purchased AI software).

 

I get the error without ActiveSky Next running (not in use).

 

 Maybe there are default Military AI .. I never checked (FSX or P3D).

 

 

*** But, VOXatc should not be shutting down no matter what Ai are doing.

Share this post


Link to post
Share on other sites

THANK YOU. I removed all military and GA from my Sim Object folder not just the scenery files and haven't had one since. I was having Fatal Errors at FSdreamteam LSZH right after "Line up" instructions or after take off and now no more. Which I think solved it for me. There are still weird AI behavior at certain addon airports but they never cause fatal errors.

Most welcome.

"I used to get fatal errors with addon AI traffic (traffic x)"

 

 Is this (traffic x) a purchased product from Just Flight?

 Did you have the errors in all previous versions and current version 6.49 of VOXatc?

 did you have errors in FSX and P3D V2.4?

 

 

 

"I removed all military and GA from my Sim Object folder not just the scenery files and haven't had one since. I was having Fatal Errors at FSdreamteam LSZH right after "Line up" instructions or after take off and now no more."

 

 And, my VOXatc errors are in FSX and P3D .. my P3D only has default AI (no purchased AI software).

 

I get the error without ActiveSky Next running (not in use).

 

 Maybe there are default Military AI .. I never checked (FSX or P3D).

 

 

*** But, VOXatc should not be shutting down no matter what Ai are doing.

Yes, MyTraffic 2010 (Just Flight), I only own FSX. Apparently, fsx is prone to crash when an aircraft goes supersonic, despite weather you have Vox or not. However, Vox tends to spawn more military AI than usual (settings and location pending), so crashes appear to be more frequent than usual, especially, if you are located at a military specific location. I do not concidor it to be a Vox issue.

FSX Voxatc v6.49 / FSX fatal error departing KDTW for a flight to KCLE (screenshot sequence is in this short video).

 

P3D v2.4  Voxatc v6.49 fatal error while taxiing out for a KDTW departure to KCLE.VOXatc-p3d-error-1_zps31d780da.jpg

 

Right click on screen just before fatal error, check AI aircraft for any military aircraft ?

Share this post


Link to post
Share on other sites

I have MyTrafficX (different developer).

 

Would you think it would be the same type error?

 

Also ... I get the error with P3D V2.4 with default AI traffic.

 

VOXatc .. if it has an error there should be a solution ... my guess.

Share this post


Link to post
Share on other sites

I have MyTrafficX (different developer).

 

Would you think it would be the same type error?

 

Also ... I get the error with P3D V2.4 with default AI traffic.

 

VOXatc .. if it has an error there should be a solution ... my guess.

I would think so, check AI prior to fatal error for military A/C ?

Share this post


Link to post
Share on other sites

Ok,

 

"I would think so, check AI prior to fatal error for military A/C ?"

 

How do I do that?

Share this post


Link to post
Share on other sites

Ok,

 

"I would think so, check AI prior to fatal error for military A/C ?"

 

How do I do that?

Right click on empty part of screen, click on aircraft/AI aircraft, and have a look at the list of aircraft that Vox has spawned for you. Any military aircraft will crash Vox, not just supersonics. Or set Vox Traffic to zero and test ?

Share this post


Link to post
Share on other sites

Ok,

 

"Or set Vox Traffic to zero and test"

That would be easiest!

 

Will do.

Share this post


Link to post
Share on other sites

"Right click on empty part of screen, click on aircraft/AI aircraft"

 

On my setup Rt-Clk then select "Traffic" from the drop down and it only shows if FSX traffic slider is not at zero.

 

I did another test with zero FSX traffic (as usual) and zero Voxatc traffic for the test (set prior to starting FSX).

 

I selected a different dep rwy. All normal for ATC and taxi to rwy.

 

Cleared for takeoff ... told go to 6000 feet.

 

 

Takeoff to about 1200 feet and Fatal Error.

 

Also my autopilot controlls HDG etc locked up and I could not use the "K" key ....

ATC kept asking Could I read them ....

I disabled VOXatc.

 

Now my autopilot etc was all working again.

 

Strange stuff!

 

I took a bunch of screenshots if needed.

Share this post


Link to post
Share on other sites

It can't be an A/I traffic issue then. When you reinstalled Vox, did you remove the internal workings files ?

Share this post


Link to post
Share on other sites

"It can't be an A/I traffic issue then."

Correct.

Or, a sonic boom.

 

"When you reinstalled Vox, did you remove the internal workings files ?"

No.

Where does it say when should be done?

Share this post


Link to post
Share on other sites

Internal workings is the last remenents of Vox after uninstall, it is in two or three locations.

Once deleted, you will need to re-register, and re configer Vox. This has fixed issues with Vox for me in the past. Makes for a clean install. I also remove all voices and voxpop. I do not start voxpop at all, ever. I never have fatal errors, ever.

 

Good luck

Share this post


Link to post
Share on other sites

"Internal workings"

 

Is the main folder for VOXatc.

 

Maybe the developer need to mention your procedure in his manual.

 

I departed from another airport (KDET) near the problem airport KDTW ... no problems.

 

I sent the developer the problem log a couple days ago (at his request).

Waiting now to see what he finds caused the Fatal Error.

 

I have previously installed other versions of the software without problem.

 

 

Edit:

"Internal workings is the last remenents of Vox after uninstall, it is in two or three locations.
Once deleted, you will need to re-register, and re configer Vox. This has fixed issues with Vox for me in the past."

 

What issues required you to do a reinstall ... that fixed them?

Share this post


Link to post
Share on other sites

I do not start voxpop at all, ever. I never have fatal errors, ever.

Good luck

What do you mean by that?

 

Do you mean that you never assign voxpop voices and never use them?

Share this post


Link to post
Share on other sites

What do you mean by that?

Do you mean that you never assign voxpop voices and never use them?

I have all the voxpop voices installed and two ivona voices. I install voxpop app, but i do not run it as it crashes every time. I have tried NOT installing voxpop app (as I do not run it), however, Vox crashes without it installed. I have all the voxpop voices assigned to pilot voices (including micro Anna) and the ivona voices assigned to ATC. I do not run voxpop app to load voices into memory, I just enable Vox ingame. It takes a little while longer to load the voices into memory (but not much). Keep in mind, you need plenty surplus memory to run so many voices, so just start with a couple.

"Internal workings"

 

What issues required you to do a reinstall ... that fixed them?

Constant fatal errors.

"

 

What issues required you to do a reinstall ... that fixed them?

Constant fatal errors.

Share this post


Link to post
Share on other sites

The developer found out what caused my KDTW-KCLE Fatal Error on departure climb out.

 

It was the PALCE7 SID.

 

It is now being fixed.

Share this post


Link to post
Share on other sites

The developer found out what caused my KDTW-KCLE Fatal Error on departure climb out.

 

It was the PALCE7 SID.

 

It is now being fixed.

Great news

Share this post


Link to post
Share on other sites

What do you mean by that?

Do you mean that you never assign voxpop voices and never use them?

In a nut shell, you install VOXPOP server and the " never" touch it again. It just need's to be there and that's it.

 

The only thing you need to do is set up your flight plan and FSX and start VoxAtc when you are ready. The only thing I do differently is before starting FSX and getting into a flight, I go into the the VOXATC voice configurator (I have a shortcut on my desktop) and run all my voices ( especially the Voxpop ones). This speeds up the initialization process when starting Voxatc at the start of my flight. Note: you only have to do this once after booting up your rig.

Regards,

Share this post


Link to post
Share on other sites

I'm getting voxatc fatal errors with Active sky next with the service packs; I have no added traffics. I have noticed that when I look at the view/instrument panel VATC and recent coms options are listed twice, once above AND below ASN X Guage

Share this post


Link to post
Share on other sites

I'm getting voxatc fatal errors with Active sky next with the service packs; I have no added traffics. I have noticed that when I look at the view/instrument panel VATC and recent coms options are listed twice, once above AND below ASN X Guage

 

What happens if you do not use the ASN XGauge?

 

What happens if you use the keyboard key "J" to get Recent Comms?

 

Do you only get the Fatal Error when asking fo recent comms?

 

Can it happen at any airport (location/situation)/

 

Did you tell the developer?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this