Jump to content
The simFlight Network Forums

Oliver Grützmann

Members
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Oliver Grützmann

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Berlin
  1. FSUIPC5 / RunIf not recognizing running programs

    Hey Pete, thanks for the fix and the support you offer :) Oliver
  2. Hi, I've been using RunIf to start some programs in FSUIPC 4 and simply copied the [Programs] section over: [Programs] RunIf1=CLOSE,HIDE,"C:\Users\Olli\AppData\Local\vPilot\vPilot.exe -host -voice" RunIf2="C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe" RunIf3=HIDE,"C:\Program Files (x86)\Landing Rate Monitor\LRM.exe" RunIf4="C:\Program Files (x86)\Navigraph\Simlink\NavigraphSimlink.exe" this worked well before, but in v5 those commands are executed on every start, no matter if the programs are running or not. TrackIR and NavigraphSimlink are not reacting to the CLOSE parameter (and I removed it), so they remain open and present me an angry "I'm already running!" message. Anything else I can do? I attatched my logfile in case it helps. Oliver. FSUIPC5.log
  3. Makerwy.zip

    Same here with Windows Defender. I checked the file at virustotal.com, looks like a false positive: https://virustotal.com/de/file/78e50c209a6e52d1ac3eb07b783263577218aba457a70b2e6452098dac1b8742/analysis/1470604331/ Oliver.
  4. Hook Errors/P3D v3.2

    Hi, I see those Hook Errors as well, but fortunately, they only happen when I close Prepar3D. No crash during flight so far. Happens after longer flights only, never while doing some short tests on the ground. Let me know if some tests on my system can be of any help.
  5. Prepar3D crashing with 4.949f

    Hi, me again. Looks like I might have sorted the error out. Seems like it was one corrupt AI model which never appeared before. Must have hit this model (or at least a similar one, which vPilot matched to this model) in two subsequent flights just after installing the new version of FSUIPC. I was able to reproduce the exact same error by running the model matching check of vPilot. Looks solved. Thanks for your help here. Oliver.
  6. Prepar3D crashing with 4.949f

    Hi, found Mytraffic as well, but I don't use it. What I also found was the term "stackhash" in the error log, which, it seems, can be caused by almost anything. Maybe it's really just coincidence that this started after installing a new FSUIPC Version. I'm currently doing some testing, but (un)fortunately unable to reproduce for now (2 hrs of flight). Worst thing is being absolutely clueless.
  7. Prepar3D crashing with 4.949f

    Hi Pete, thanks alot. In that case I'm sure I had the .949c version. It's more about testing, if I know that it's coming with FSUIPC I can give LM something to start with. Else I know I need to look elsewhere. For me it's the easiest to roll back the change I made before the problem occured. If it's still there, at least I have one thing ruled out. I'll send you my email via PM. Oliver.
  8. Prepar3D crashing with 4.949f

    He Pete, thanks for your reply. FSUIPC was my first guess, it started just after the upgrade. Previous was 4.949c or later, not sure if there was a version in between. I checked last monday and there was no update available. As mentioned, nothing else changed but FSUIPC. No new scenery, no other modules, no settings, no cfg tweaks, no Windows updates, nothing. I was shutting down my computer after one flight, booted later on, installed FSUIPC .949f and started a flight with the mentioned result. I had a rock solid P3D before, no crashes at all. No, I'm not using autosave. Had no use for it, since I never experienced any crashes or OOMs. Is there any chance to get back to 4.949c to start sorting out the error? At least I could rule out or confirm that it's in some way related to it (and, if so, at least get back to a stable sim). I'm at work currently, but I'll do some testing back at home. What I found in LM forums was someone mentioning saitek drivers. Maybe it is somehow related to this and the upgrade. Have to admit, I'm completely clueless - from absolutely stable to constantly crashing within a few hours. Oliver.
  9. Hi, since installing FSUIPC 4.949f I get Prepar3D crashes in every flight referencing ntdll.dll. It might be related to FSUIPC, in fact it started just after installing 4.949f (I was doing a 2.5 hrs flight without problems, shutting down my PC, out for a walk, starting my PC, installing .949f and doing a flight). It's a hard CTD, so there's no hint in the log file. The crash happens randomly (first flight it was after 30 minutes, second after 1.5 hrs). Really no changes but FSUIPC, same programs running (FS Global Real Weather and FS RealTime via widefs). Could this be caused by the changes in the lua code? I'm using DynamicFriction.lua Any ideas? Oliver. Here's the log of FSUIPC and the appcrash itself: ********* FSUIPC4, Version 4.949f by Pete Dowson ********* Prepar3D.exe version = 3.1.2.15831 Reading options from "D:\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=57CE0000 FSUIPC4 Key is provided WideFS7 Key is provided 312 System time = 14/02/2016 22:44:59 328 FLT UNC path = "\\VIRUS\Users\Olli\Documents\Prepar3D v3 Files\" 328 ------ Module Version Check ------ 328 acontain.dll: 3.1.2.15831 328 api.dll: 3.1.2.15831 328 controls.dll: 3.1.2.15831 328 fs-traffic.dll: 3.1.2.15831 328 G3D.dll: 3.1.2.15831 328 language.dll: 3.1.2.15831 328 sim1.dll: 3.1.2.15831 328 visualfx.dll: 3.1.2.15831 328 weather.dll: 3.1.2.15831 328 window.dll: 3.1.2.15831 328 ---------------------------------- 328 Trying D:\Prepar3D v3\Modules\SimConnectP3D2.dll 328 Found it: trying to connect 344 FS UNC path = "\\VIRUS\Prepar3D v3\" 500 ---------------------- Joystick Device Scan ----------------------- 500 Product= Saitek X52 Pro Flight Control System 500 Manufacturer= Saitek 500 Vendor=06A3, Product=0762 (Version 0.48) 500 Serial Number= Saitek 500 ------------------------------------------------------------------- 515 LogOptions=00000000 00000001 515 ------------------------------------------------------------------- 515 ------ Setting the hooks and direct calls into the simulator ------ 515 --- CONTROLS timer memory location obtained ok 515 --- SIM1 Frictions access gained 515 --- FS Controls Table located ok 515 --- Installed Mouse Macro hooks ok. 515 --- Wind smoothing fix is installed 515 --- SimConnect intercept for texts and menus installed ok 515 --- All links okay (except older global weather setting method) 515 ------------------------------------------------------------------- 515 SimConnect_Open succeeded: waiting to check version okay 515 Trying to use SimConnect Prepar3D 39687 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 39687 Initialising SimConnect data requests now 39687 FSUIPC Menu entry added 39703 \\VIRUS\Users\Olli\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 39703 \\VIRUS\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 59265 Weather Mode now = Theme 72781 \\VIRUS\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 86797 System time = 14/02/2016 22:46:25, Simulator time = 08:00:00 (13:00Z) 86812 Aircraft="Boeing 737-8K5NGX airberlin Winglets" 87797 Starting everything now ... 91297 Advanced Weather Interface Enabled 299297 Weather Mode now = Global 299297 Weather Mode now = Custom 906500 Weather Mode now = Global 906500 Weather Mode now = Custom 3187390 Sim stopped: average frame rate for last 3012 secs = 47.9 fps 3407265 Sim stopped: average frame rate for last 209 secs = 59.7 fps 3650390 Sim stopped: average frame rate for last 240 secs = 59.6 fps Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.1.2.15831, Zeitstempel: 0x5672b60a Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.10586.103, Zeitstempel: 0x56a853dc Ausnahmecode: 0xc0000374 Fehleroffset: 0x000dc759 ID des fehlerhaften Prozesses: 0x1ebc Startzeit der fehlerhaften Anwendung: 0x01d16770ee6604ac Pfad der fehlerhaften Anwendung: D:\Prepar3D v3\Prepar3D.exe Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
  10. The log file from FSUIPC won't tell you anything if P3D is simply hanging when WideFS tries to shut down. There's nothing it can log. The thread shutdown is just a simply call to Windows. If it doesn't return then that's it. Pete Hi Pete, I thought so as well, and it seems to be true. Looks a bit strange anyway, like the sim closing and coming up again. I'd suspect some windows update, or something in the P3D code that makes this happen just now. Just for information, here's the FSUIPC log. Don't think it's related or helpful here. :) ********* FSUIPC4, Version 4.949a by Pete Dowson ********* Prepar3D.exe version = 3.1.2.15831 Reading options from "D:\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=5DF10000 FSUIPC4 Key is provided WideFS7 Key is provided 266 System time = 17/01/2016 17:13:51 266 FLT UNC path = "C:\Users\Olli\Documents\Prepar3D v3 Files\" 266 ------ Module Version Check ------ 266 acontain.dll: 3.1.2.15831 266 api.dll: 3.1.2.15831 266 controls.dll: 3.1.2.15831 266 fs-traffic.dll: 3.1.2.15831 266 G3D.dll: 3.1.2.15831 266 sim1.dll: 3.1.2.15831 266 visualfx.dll: 3.1.2.15831 266 weather.dll: 3.1.2.15831 266 window.dll: 3.1.2.15831 266 ---------------------------------- 266 Trying D:\Prepar3D v3\Modules\SimConnectP3D2.dll 266 Found it: trying to connect 297 FS UNC path = "\\VIRUS\Prepar3D v3\" 375 ---------------------- Joystick Device Scan ----------------------- 375 Product= Saitek X52 Pro Flight Control System 375 Manufacturer= Saitek 375 Vendor=06A3, Product=0762 (Version 0.48) 375 Serial Number= Saitek 375 ------------------------------------------------------------------- 391 LogOptions=00000000 00000001 391 ------------------------------------------------------------------- 391 ------ Setting the hooks and direct calls into the simulator ------ 391 --- CONTROLS timer memory location obtained ok 391 --- SIM1 Frictions access gained 391 --- FS Controls Table located ok 391 --- Installed Mouse Macro hooks ok. 391 --- Wind smoothing fix is installed 391 --- All links okay (except older global weather setting method) 391 ------------------------------------------------------------------- 391 SimConnect_Open succeeded: waiting to check version okay 391 Trying to use SimConnect Prepar3D 1797 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 1797 Initialising SimConnect data requests now 1797 FSUIPC Menu entry added 1828 C:\Users\Olli\Documents\Prepar3D v3 Files\Default.fxml 1828 \\VIRUS\Prepar3D v3\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.air 36063 \\VIRUS\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 49657 System time = 17/01/2016 17:14:40, Simulator time = 17:14:23 (16:14Z) 49657 Aircraft="Boeing 737-8K5NGX airberlin Winglets" 50657 Starting everything now ... 54828 Advanced Weather Interface Enabled 224828 Weather Mode now = Global 224828 Weather Mode now = Custom 833828 Weather Mode now = Global 833828 Weather Mode now = Custom 1434250 Weather Mode now = Global 1434250 Weather Mode now = Custom 2034672 Weather Mode now = Global 2034672 Weather Mode now = Custom 9221969 Sim stopped: average frame rate for last 9173 secs = 59.9 fps 13982453 Weather Mode now = Global 13982578 Weather Mode now = Custom 14112297 Weather Mode now = Global 14112297 **** No SimConnect events or states being received! Re-connecting now ... **** 14112391 SimConnect_Open succeeded: waiting to check version okay 14112407 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 14112407 Initialising SimConnect data requests now 14112407 FSUIPC Menu entry added 14112828 System time = 17/01/2016 21:09:03, Simulator time = 21:09:48 (20:09Z) 14169453 Sim stopped: average frame rate for last 57 secs = 39.1 fps Oliver.
  11. Hi, strange thing, same on my installation starting today. Relatively fresh install of Win 10 x64, P3D v3.1, FSUIPC 4.949a + WideFS (did not install c, yet). Only thing I did today was some tweaking in Prepar3D.ini (nothing I didn't do before, just deleted that file and started over). No change in any other part of P3D or FSUIPC.ini, no new addons - simply nothing. Never noticed this behaviour before, and I'm not sure if it's really related to wideFS, just noticed it today and saw this thread created yesterday. I'm currently doing a flight. If it happens again, I will check the log files afterwards. Oliver.
  12. For me the FSUIPC control to disconnect the autopilot works perfectly in the NGX. Didn't have to assign any keystrokes. Oliver.
  13. PMDG 737NGX to SQUAWKBOX 4 mode sel

    If someone is interested: I've written a version that uses ident as well. http://forums.vatsim.net/viewtopic.php?f=39&t=62999#p455697 or https://www.dropbox.com/s/ekpb7ucm3mwix1k/Transponder_NGX.zip
×