Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unable to use 6.46 due to internal error

Featured Replies

  Installed 6.46.  Ran it initially to allow it to build all the database.  Flew a couple of flights.  All was well.  Installed a couple of new a/c.  Re-ran the Indexer to add them to the database.  Now getting this error in the log:

 

Log Start 07/06/2014 11:19:30

Object reference not set to an instance of an object.
   at com.intworkings.voxatc.CallsignImpl.CreateNCallsign(String idIn, AircraftType aTypeIn)
   at com.intworkings.voxatc.CallsignImpl.CreateUserCallsign(String idIn, AircraftType typeIn)
   at VoxATCServer.VoxATCServer.SetupLocalFlightPlan()
   at VoxATCServer.VoxATCServer.InitVoxAtc()
 

 

 

   Don't tell me much but it looks like it has to do with the callsign (in this case JetBlue).  Any clues?

 

-Rick

Rick,

 

Are you using P3D Ver??

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Author

  No sir.  FSX.  The old version (before 6.45) did not have this problem.

 

-Rick

Rick,

"Installed a couple of new a/c"

Which ones?

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Author

I installed 2.  One was a repaint for my PMDG 777 and the other was a repaint for the FT A320 IAE version.  It's the FT one that's not being recognized.  Here's the aircraft.cfg entry for that particular plane:

 

[fltsim.1]
title=Feelthere A320 IAE Airbus JetBlue "Blues Brothers"
sim=FeelThere_A320IAE
model=
panel=
sound=
texture=BlBro
kb_checklists=
kb_reference=topcat
atc_id=NNNNN
atc_id_color=
atc_parking_types=
ui_manufacturer=feelThere/Wilco Airbus Series Vol 1
ui_type=A320 IAE
ui_variation=JetBlue "Blues Brothers"
description=Airbus 320-214\nfeelThere/Wilco (Dual Class)\n06 JUL 2014 09:36 UTC\n\nConfigured by TOPCAT\n\nPassengers\t\t129+5\nCargo\t\t\t13789 lb\n\nDry Operating Weight\t94950 lb\nZero Fuel Weight\t\t132280 lb\nTake-Off Fuel\t\t27100 lb\nTake-Off Weight\t\t159380 lb\nTake-Off MAC\t\t25.6%\nStabilizer Trim\t\t0.6 UP\n
ui_typerole=Commercial Airliner
ui_createdby=feelThere/Wilco
atc_heavy=0
atc_airline=JetBlue
atc_flight_number=1864
visual_damage=1

 

-Rick

Rick,

 

Wonder why the quotes "" "Blues Brothers".

 

Which fields are different in FT compared to all other aircraft?

e.g. atc_id=NNNNN

 

 

 

I thought I might have the aircraft you added but I do not.

 

The FT load up ok on its own in FSX?

 

How about the VOXatc modified both Panel files 777 vs FT ... any special stuff in FT?

Did the correct FT panel file get modified?

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Author

I removed the quotes (was added by the installer from Wilco for the a/c) and the error stopped.  Guess they need to add a check for that when the scan the a/c, huh?   :-)

 

-Rick

Rick,

 

Also, "[fltsim.1] " the number 0, 1, 2, 3 is important ..

a repaint added to the aircraft.cfg will be the next higher number in your aircraft.cfg list of aircraft.

 

Have a good flight.

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Author

Yup, I know.  Been flight-simming since FS98.   :t4020:   For some reason a Wilco installer add all the new installed repaints to the END of the config file instead of towards the front.  Go figure.  .0 is up at the top and is the initial unpainted one that comes with the install.  Catch ya later.

 

-Rick

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.