Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

canuck21a

members
  • Content Count

    70
  • Joined

  • Last visited

Community Reputation

12 Good

About canuck21a

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

1753 profile views
  1. This is the version that was installed: I will check to see if there is a newer version. I seems that maybe this is the latest. I have also updated Windows to build 1903 recently. When I start Simstarter today I get no obvious errors.
  2. Here is what I was able to "copy": See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.InvalidCastException: Operator '<' is not defined for type 'DBNull' and string "184". at Microsoft.VisualBasic.CompilerServices.Operators.ConditionalCompareObjectLess(Object Left, Object Right, Boolean TextCompare) at .(Object , Object , Boolean ) at SIMstarter_NG.sceneryTable_F.(Object ) at (Object , Object ) at .(Object , Object ) at SIMstarter_NG.sceneryTable_F.readSceneryCfg(file scenery_file, Boolean addAddOnXml_BL) at (Object , file , Boolean ) at .(Object , file , Boolean ) at .() at .() at .(Form ) at .(Form ) at .(Boolean , Boolean , Form ) at .(Boolean , Boolean , Form ) at SIMstarter_NG.startPos_F.get_addOnAirports(Form target_F, Boolean refresh_BL) at (Object , Form , Boolean ) at .(Object , Form , Boolean ) at .(Form ) at .(Form ) at SIMstarter_NG.main_F.(Object , EventArgs ) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- SIMstarter NG Assembly Version: 1.8.7.1 Win32 Version: 1.8.7.1 CodeBase: file:///E:/aerosoft/SIMstarter%20NG/SIMstarter%20NG.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3362.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- ? Assembly Version: 0.0.0.0 Win32 Version: 1.8.7.1 CodeBase: file:///E:/aerosoft/SIMstarter%20NG/SIMstarter%20NG.exe ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.IO.Compression.FileSystem Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression.FileSystem/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.FileSystem.dll ---------------------------------------- System.IO.Compression Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  3. I have just installed Simstarter on a rebuilt system with P3D v4.5. When starting I get this error: I can select "Continue" and the app seems to carry on. I am not comfortable with trying to change any P3D scenery items with this error popping up. Any suggestions?
  4. Thanks for the reply Rolf, I shall see how that works out then next time I mess things up.
  5. Hello, My question today has to do with how a user can recover from a botched flight plan. Sometimes a flight plan gets messed up and it is best to start over. I have tried resetting the state to where it started but the messy plan is still there. So far the only way I have found to do so is to exit P3D and start over. This seems drastic and there may likely be a known way to get the MCDU back to the init state. Unfortunately my searches have yet to find a reference to such a procedure.
  6. Thanks for the reply and clarification. All the best, Darryl
  7. Running 1.2.3.2 If my memory is correct the previous update provided an option to disable GSX taxi in favour of the default. I had used this when things did not go well with the GSX taxi. I could shut it off and continue. Today I noticed that the option was no longer where it was before ? Has it been moved or removed?
  8. Just had an event today after many flights with no issues...... Operating System: Windows 10 Pro Ver 1803 Build 17134.472 Simulator version: P3D v4.4 (4.416.27077) Airbus version: Updater: 1.3.0.1 A320 1.2.3.1 Add-ons in use: FSUIPC5 (FS-Products ACARS), Navigraph 1902, ORBX SC/NC/NRM/PNW (Note: Clear Skies ASP4 is installed/available but not enabled on this flight) System specs: Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied.  Description of the issue: Flight Plan Extended: YPPH N0120F360 KEELS5 MERIB T12 XMX G209 TKG CARL1A WIII During the Descent phase the PFD speed dropped to 190 although it should have been B280 according to the STAR. It almost looks like it decided to use the Approach speed. I also noticed that the speed select indicator on the PFD kept jumping up and back down as if it wanted to go up but was being told to keep down during this period. I changed to using the manual speed knob during the descent and all was well. I switched to managed speed when the speed was to be at 190. The rest of the flight was normal. Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? After at least 8 flights with no issues this happened. Additional information (route, weights, special area where the issue occurred etc.): I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time. A320_Data_DRW_2019-Feb-19.zip
  9. Just read this..... Back in December I made several flights with the A320 using airways that crossed the BOI waypoint. I had speed control issues somewhere around that point as well. Wondering if there are potential Navigraph issues?
  10. Now getting back after my manually entered constraints. YSSYYMML01 64LOC ANKUB SBKWI KADOM A576 PKS Q94 CANTY ARBE2A Each of the first four departure waypoints were given different altitudes and speeds. AP was engaged before 64LOC. All speeds and altitudes were maintained. This is something that I had yet to see with the new bus. The ND markers also seemed to match the plan. I will now have a look at injecting weather to see if that has any effect.
  11. Hello again, I have now completed two more flights with the A320 United. The last flight was from Brisbane to Sydney at FL340 HUUG06 HUUGO H62 CORKY H12 BOREE BORE9P Rwy 19 to 16R Weather was CAVOK with no external weather engine. I used Navigraph 1902. I did use my multiplayer JoinFS (simconnect) and my ACARS (FSUIPC) with flight saves every 30 minutes. I had full logging turned on. The SID contained a speed restriction while the STAR had both BxxxxAxxxx and specific altitudes. It also had a speed restriction at one STAR waypoint. This seemed to have everything in it that had not worked in previous versions. In full managed mode for the entire flight every speed restriction was met as were all of the altitudes. It is hard to complain when everything seems to be working. My next flight will use manual restrictions for speed and altitude to see if there is a difference between Navigraph generated characteristics and manually entered ones. One thing that I continue to see is the MCDU showing an altitude that does not match the one that is being flown. Image attached showing two mcdu views for the same waypoint.
  12. Greetings, I have waited quietly in the wings in anticipation of the new "full" version. I removed both of the full installs (A318/319) & (A320.321). I also removed all folders in "My Documents" that had anything to do with Aerosoft. I then purged all remnants using CCleaner followed by a defrag. A reboot was completed. I then installed the new versions and rebooted. I then updated my Navigraph. I added no paints. Today I tried my first flight with the A319. A plan was created in Australia YPDNYPTN14 with SID LAKUP4 and a ILS-Y OM14 approach. The level was FL190. The departure had an altitude restriction A3000 and B5000 at different waypoints along with a 600 foot intersection turn after takeoff. A bit of a task. After take off the AP was turned on just before the A600 waypoint. The copilot and flight system worked flawlessly. I watched with hands off and the plane climbed to 5000 and stayed there until it passed the ALT restriction. Just after passing the plane started to climb to 10000. It levelled off a bit at 10000 and allowed the speed to reach 300 then began a feisty ascent to FL190. At TOD it started to descend and also reduced speed to ~280 (had to add some speed brakes here). After ILS Loc captured I still got the wing wave after a bit. Close to GS I enabled App. The plane flew in like a happy bird with no wing wave near the airport. So far so good....more to come later.
  13. I have just completed a return flight from CYVR to KDVT. The flight from KDVT to CYVR yesterday had no problems. On this occasion the speed problem occured. (Has happened on other flights but not all) Operating System: Windows 10 Pro Ver 1803 Build 17134.472 Simulator version: P3D v4.4 (4.416.27077) Airbus version: Updater: 1.2.2.0 A320 1.2.2.1 Add-ons in use: FSUIPC5 (FS-Products ACARS), Navigraph 1813, ORBX SC/NC/NRM/PNW (Note: Clear Skies ASP4 is installed/available but not enabled on this flight) System specs: Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied. Description of the issue: After a normal take-off and climb to Cruise the sim decided to change the cruise speed to 222. This resulted in a loss of altitude and the need to disengage AP, change to manual speed. Once recovered AP speed ,NAV and ALT were re-established. Managed speed was never recovered. Upon final approach speed was engaged for landing and all check list actions by copilot worked without issue. Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? An attempt to save all logs and a special video was tried on a previous flight but no issues occurred. Today the flight was the reverse of the previous one but no video was captured and the speed issue occurred. Other flights along a similar route have also presented this issue Additional information (route, weights, special area where the issue occurred etc.): I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time. a320troublefile1.zip
  14. Thanks for the reply. I am using the latest build. I shall await the next update to see if things change.
  15. I had posted a query regarding setting a speed constraint in a SID last weekend but no replies have come to date. Perhaps I placed it in the wrong section?
×
×
  • Create New...