Jump to content

JackSwyr

Members
  • Posts

    75
  • Joined

  • Last visited

Everything posted by JackSwyr

  1. After resetting and removing the LUA it’s working fine, for now but like I said it’s almost creepy, like the sim has a mind of its own. But I like it much better now. Thanks for all you guys’ help! Jack
  2. Ok, I quit XP, then removed the LUA script. Ran XP and reset the pedals and it “seems” to be better. It’s odd that the same settings from session to session change. I use ASXP, could it be winds causing this?
  3. They were never changed at all. All vanilla.
  4. I’ll remove that script but I disabled it in sim and no change but I’ll delete it. As for resetting all response curves, how do I do this? I have never even seen these screen till just a few minutes ago.
  5. Hi, thanks, hope this helps because I have no idea what this is or does.
  6. Yes sir, just checked. 1.1.9.
  7. Hello, it's been a while since I posted or flew. I have the latest version and the plane on taxiing acts like it's on slippery ice. I even tried a LUA script called friction_fix.lua and it's still all over the place. Does anyone else have this issue? This is with all planes too but I mostly fly the TBM 900 and I read the latest update was supposed to fix this. Thanks, Jack
  8. Thanks Dwight! Cheers and thank you for your help, it's very much appreciated.
  9. Hi Dwight. I don't even know what xSquawkBox is. As for the plane on ice, I run FlyWithLua now and there's a plug-in for it that stops this behavior so it now works flawlessly.
  10. Ok, this is what I did Dwight, I kept those two folders AND the DLL's. I started at EGHI, started the plane and still have the hassle with the FMC keyboard. I wrote down the sequence. When I hit the DIR key I get a five letter nav code, I should have written it down, but when I want to enter EGTF I type the E and get 5B, then I hit backspace and type E, then get a 5, press E again and get a 0, backspace yet again and get an E and I can now enter EGTF. I taught the G1000 for a couple of years, let me tell ya, it ain't supposed to do this but if they're using the default G1000 then I sure hope X-Plane fixes this someday. Another major problem I have with X-Plane is ALL my small planes act like they're on slick ice, I mean it's almost impossible to take off in any one of them, the TBM included. It spins around like it's on a weather vane, even at low taxi speeds, I used to fly real planes and I've never seen this. This was both before I removed the plugins and after. And I'm not even using weather. So anyway, here's my logs. I didn't look at them as I don't know what I'm looking for anyway. Thanks and your help is very much appreciated. GizmoLog.txt TBM900_Log.txt Log.txt
  11. Hi Dwight, I finally have a chance to do all this. Right now I deleted that folder and I created a folder called 000_Disabled. In it I placed: ASXPConnect (so I can’t use ASXP weather?), AviTab (which is for the Zibo 737), BetterPushback (which I haven’t used once yet), rxpGTN (which I like in two of my G/A planes), and UltraWeather XP (which I use on every flight because it has weather presets). Will UWXP net being there mess things up? Also, I did not put XPLM.framework and XPWidgets.framework folder into the disabled folder because I thought I might need them since you said to keep those dll’s. Now I’m going to try a flight in the TBM and then post the logs.
  12. Thanks Dwight, I really appreciate your help! Ok, so I create a separate folder IN the plug ins folder, will do, and will do all you say and report back as soon a real life lets me. Jack
  13. Thanks. Where do I get the log file? I’m looking in the TBM-900 folder and don’t see it. I found it, posting it now. On the iPad typing this...
  14. Ok, what I meant was the Reality XP GTN, I shut it off mid flight. I also saw the Gizmo whatever that is and have the log. So three logs are attached here. I had no CTD or other problems, she flew beautifully except for that annoying keyboard entry problem. scenery_packs.ini Log.txt GizmoLog.txt
  15. Hi Dwight, finally have to make the same flight I have been making for testing, EGPB to Wick. So far so good but I forgot to disable the RADAR plug-in first. I'll post my logs as soon as I land this thing and what is Gizmo?
  16. Many thanks Dwight but it doesn’t work at all like that for me and several other people I’ve seen in posts.
  17. Thanks, did you use the FMC keyboard because it has not once worked for me in 3D cockpit or 2D pop up.
  18. Will do as soon as it crashes again and I have a chance to fly, real life getting in the way.
  19. Was going to do this but I was told above it’s normal to see the errors in the log. Next time it crashes I’ll be sure to post the files, been too busy with real life to fly though.
  20. Well that’s good news thanks! Maybe it was the radar plug in.
  21. Here's a reply from a friend at Orbx. He posted this back to me after looking at my log. I have no idea what this means so maybe someone here can tell me. I plan on making another TBM flight very soo and posting the complete log. Hope this helps. We know the issue is not the data because it is an Xplane data file and if you remember we even reinstalled those particular files to ensure they had not become corrupted. That means this error is specific to the BM900 aircraft and in particular the way navaiddb.c:512 is reading/parsing that data. So if you flew the same route with the stock Cesna then this error should disappear from your log.txt - at least that is the way I interpret the error. However if it is still there then BobT post could offer another explanation and I would certainly ensure you have experimental flight engine unchecked as it is possible an error in that code could be throwing the error on all aircraft. If the errors are only there with the TBM900 then you might like to show them these particular errors in their help forum and see if they can better understand what is going on. "From your log.txt 2"019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2011 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2043 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2069 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2094 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2259 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2834 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3314 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4606 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5552 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5563 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5594 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5621 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5646 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5809 2019-03-31 14:26:15 TBM900[navaiddb.c:512]: Error parsing K:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6386"
  22. I will send another log later today.
  23. I’ve done everything they recommend, new video driver, removing all plug-ins, even using a new XP but still get these navdata crashes. First they blamed Orbx but it’s not them as they showed me it’s global scenery files.
  24. Think this will ever get fixed? As it stands now I get constant CTD’s. New Nvidia driver, etc. The plane keeps logging about bad navdata. Will post the log soon. I really love this plane but with all the navdata CTD’s I might bin it and write it off as a very expensive loss
×
×
  • Create New...