Jump to content

KZ1R

Members
  • Content Count

    79
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

5 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  • Virtual Airlines
    Yes

Recent Profile Visitors

826 profile views
  1. One more crash: Faulting application name: ChasePlane.exe, version: 0.1.675.0, time stamp: 0x58d34256 Faulting module name: clr.dll, version: 4.6.1590.0, time stamp: 0x5787ee4f Exception code: 0xc0000005 Fault offset: 0x001b89cf Faulting process id: 0x3120 Faulting application start time: 0x01d2a3e12337591c Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: 8397b7df-0fd6-11e7-baf5-00090ffe0001 Application: ChasePlane.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 70D489CF (70B90000) with exit code 80131506.
  2. One more message from the Event Viewer: Application: ChasePlane.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at SlimDX.DirectInput.Mouse.GetCurrentState(SlimDX.DirectInput.MouseState ByRef) at SlimDX.DirectInput.Mouse.GetCurrentState() at OP_Janet_Library.CP_Inputs.cam_input_proc() at DynamicClass.CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, System.Object) at ChasePlane.MainWindow.highFreq_timer_tick(Int32, Int32, Int32, Int32, Int32) This happened 1 second before the event above which caused the application to crash.
  3. Almost every 5-15 minutes while on the ground or in the air. This is what Windows Event Viewer shows: Faulting application name: ChasePlane.exe, version: 0.1.675.0, time stamp: 0x58d34256 Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9c1 Exception code: 0xc0000005 Fault offset: 0x000069e0 Faulting process id: 0x2980 Faulting application start time: 0x01d2a3c7b042b129 Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe Faulting module path: C:\Windows\system32\DINPUT8.dll Report Id: 1c118667-0fce-11e7-baf5-00090ffe0001 How do I get this fixed? Thanks.
  4. KZ1R

    FMS error - NZWD

    Greetings! I have planned to fly from Christchurch (NZCH) to Williams (NZWD) and got this error: https://www.dropbox.com/s/kf9ehk7400j5frq/error1.JPG?dl=0 https://www.dropbox.com/s/kf9ehk7400j5frq/error1.JPG?dl=0 Checking the Navdata file I see the following: https://www.dropbox.com/s/mq2jezqf0nycc8k/error3.JPG?dl=0 Can you help me fix this? Thanks. Mike
  5. Pronouncing "O" as "AH" with the lips stretched helped improve recognition and now the voice to text engine decodes it correctly.
  6. Ok. Already figured out a solution. Thanks, Bryan.
  7. Hi there, when I use my FS2Crew voice edition for the AXE I very often struggle with pronouncing 'off' in the check lists and having the program detect it as 'alt'. I have 'trained' the PC recognition to properly decode my speech to text but this issue remains. Any idea what can be done about it? Very annoying to me. But the software is great and I love it. Thanks.
  8. For those who are considering purchasing this plane: I have decided to get it from Carenado and give it a try. Here you can see it in "its' full glory". There you can notice some of the glitches people were writing about in this thread. I hope it will help you make an informed decision. www.youtube.com/watch?v=Djzud0yAUuQ Regards, Mike
  9. Thanks for the review, Seith. Frankly I am not surprised to read about all the 'hiccups' in the model. As it has been seen on a number of occasions, Carenado does not pay due attention to details related to important aircraft systems and releases products constantly failing behind expectations of serious flight simmers. The reason as it seems maybe the poor project management practices or the deliberate choice of not paying attention to systems fidelity. I guess whatever the issue it resides with the Carenado's leadership. IMHO I will refrain from buying this product from them at least for the time being until they come up with patches for the issues you have described. Sad to see they don't learn from their previous experience! Regards, Mike
  10. After installing 3.2.1 shaders and dark bkg.bmp the problem is gone. I can see all the MTL traffic now. Thanks to everyone! Mike
  11. Sounds good, Fritz. I have installed the new shaders and will check them out shortly. Thanks. Mike
  12. Not yet, Paul. Will it help matters?
  13. As some of you may know, using DX10 and IVAO MTL results in seeing airplanes all white and untextured. Any idea how to fix this? If someone could describe the algorithm I would create a software application that does that. Thanks Mike
×
×
  • Create New...