mm212hd130

There's a set containing VKB rudder pedals on FB Marketplace, been there a while so maybe the guy would be willing to sell the pedals alone... Not sure if I'm allowed to share that kind of link here so I'm sending you a PM.

still working fine! problem solved :)

thanks a lot for having a look! I'm not sure if my problem is fixed, need to test more, but I was able to stay in the air 30+ minutes without crashing, and without the sim crashing either :thumbup: I did that twice so I got a good feeling about this (the sim used to crash 2-5 minutes after starting the flight) the only thing I did was to remove Nvidia GeForce Experience from my system since I didn't use it... I'll keep you posted in the next few days, in the meantime don't spend time looking into my logs! thanks again SiThSpAwN and c0ff!

tried using the TF-51D and to uncheck full screen in the options following somebody's advice, no luck! any ideas guys? I'd downgrade to 1.2.8 but I bought the F-86 to use it... Logs.zip

another one, almost identical but not 100%... Logs.zip

still crashes after reinstalling the drivers of all my USB devices see attached logs Logs.zip

I tried to find what triggers it but could not, I usually only move my stick and rudder when it occurs, it's not when changing views or when explosions or contrails appear, it can happen over a dense city or over the ocean with no 3d object around... attached are my logs in a RAR archive (maybe better on your Mac) EDIT : seems like my ZIP file is corrupted DCS crash logs.rar

I have checked but will double check, but I'm not sure how to tell if a driver is not fine since all my devices seem to work properly outside of DCS... any tips/advice?

thanks for the tip, but I only tried with my other A-10 recently... (the one with the nice MFDs that is) not sure if it helps, but I also encountered the crashes with only DCS World and the Sabre installed (it's the first module I put on my fresh install)

before somebody notices, I forgot to mention my Nvidia drivers are Beta, but my issues began when I was still using the latest stable release ( 337.88 )

tried the Warthog, Sabre and Mustang, was too pissed to try the others :D

trying to attach logs again DCS%20crash%20logs.zip

yes, 100% mod free

Hello fellow pilots, Since I installed 1.2.9, DCS crashes and goes back to the debriefing window every time I try to fly, usually within the first 5 minutes of the flight. Everything worked fine with 1.2.8, then I upgraded to 1.2.9 when I bought the F86. The crashes occur no matter which mission or aircraft I choose. I tried repairing DCS (didn't change anything), deleting my DCS Saved Games (same result), repaired C++ stuff and DirectX too, no luck. I have not modified my hardware config or drivers recently. I decided to uninstall DCS and my modules and reinstall 1.2.9 from scratch (after deleting the DCS folder to avoid keeping leftovers) but the crashes still occur. I'm running out of ideas, but maybe one of you will find something useful in the logs attached to this post. I'm using Windows 8.1 Professional ‎(X64)‎, got a Intel Core i5 3570K CPU, 8 GB of RAM, a NVIDIA GeForce GTX 780 (340.43 drivers) Thanks in advance for having a look, and happy landings!

hey Brian looks like there is a space in your filename telemetryUH1H .lua might be the issue!

hey Brian, I don't see "dofile" at the beginning of the last line of your Export.lau file, might be the problem here... :smilewink:

great!

thanks for these UH-1H instruments Leon! :thumbup: they work fine on my tablet and android phone too I'm glad you made them since I've been using the Huey a lot more than the Mustang lately... Fuby the RPM gauge becomes a Fuel gauge when you click on it

here you go : https://play.google.com/store/apps/details?id=com.portman.tews

glad it now works Fuby!

hey Fuby, - $HOME is your Windows user folder, for instance C:\Users\Fuby\, it already exists and contains several folders (My Documents, My Pictures, Saved Games...) - the brackets should not be included, just your username (Fuby or John Doe or whatever...) - telemetry and export.lua don't need to be on the tablet - as Leon said earlier, try to open a command prompt on the computer and ping your tablet to see if you get a response I hope this helps!

serial : #01469 location : near Paris, France issues : - throttle stopped working a few days after purchase, so it did a quick round trip to the factory where it was unbricked - pinky switch was loose from the beginning, after a few months it failed completely (no resistance at all now) - after a year, a few wires of the ribbon cable connecting the right throttle buttons to the main board got tired of bending and broke, need to replace that...

I guess that is the issue, works fine on a 7-inch Samsung Galaxy 2 or Nexus 7, even on Android phones... Maybe you can flash ICS on your Kindle, but that may be complicated and may void your warranty.

thanks for your reply Leon, not sure what happened last time but everything works fine today just tried to ping, checked the .lua files for typos, launched the app and voila! tried both P-51 and UH-1 telemetry files, no particular issue except gauges stop working when switching to an outside view and start working again when getting back in the cockpit... But I'm pretty sure you knew already... thanks again for your great app, can't wait for the next versions! keep up the good work! P.S. : I didn't change anything either in default config.lua/network.cfg

Thanks for the app Leon, seems great. Have not been able to make it work yet though, starts fine on my Nexus 7 but does not seem to receive data (gauges do not update at all). Tried with P-51 and UH-1, same result. I double checked I did what is explained in the instructions and searched on the forum but could not make things work. I am running DCS 1.2.4 though, and maybe this could be the issue, should I use the paths and .lua files from your instructions, or has anything changed ? export.lua and telemetry.lua are in C:\Users\$$$$$\Saved Games\DCS\Scripts and edited properly Not sure if I have to set EnableExportScript = true in Config.lua or in Network.cfg or if it is not needed, tried the different possibilities but it did not help... Any ideas guys?