Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jannier

  • Rank
    Advanced Member
  • Birthday 05/31/1968

Profile Information

  • Gender
  • Location
    Cape Town: South Africa
  • Interests
    Aviation, Flight Simulation
  1. Hi, As Thomas correctly indicated he must install the latest version 3.999z9b, because 3.999z8 expired at end of 2015 and in January 2016 you extended it to 2025 with 3.999z9b. The iFly aircraft works with registered or un-registered version of FSUIPC but the iFly aircraft checks for a legal copy of fsuipc if a registered version is being used and since he is using 3.999z8 that expired end of 2015 it thinks the key is invalid/illegal. So just a install of 3.999z9b http://fsuipc.simflight.com/beta/Install_FSUIPC3999z9b.zip should fix his problem.
  2. Hi Pete, There is now another post over at LM forums regarding this. http://www.prepar3d.com/forum/viewtopic.php?f=6314&t=125549 LM's Mike Schroeter comments here: http://www.prepar3d.com/forum/viewtopic.php?f=6314&t=125549#p161753 I just wonder why this error only appears with FSUIPC installed. FSUIPC not installed or disabled = no payload content error FSUIPC installed and enabled = payload content error on ALL aircraft default, freeware or payware Jannie
  3. Hi Pete, After updating P3D v4 with Hotfix 1 the content error happens. FSUIPC updated to v5.103 If fsuipc is disabled then there is no more this content error about station load. [error.0] error=Payload station indexes should be between 1 - Number of Stations [error.1] error=Payload station indexes should be between 1 - Number of Stations [error.2] error=Payload station indexes should be between 1 - Number of Stations [error.3] error=Payload station indexes should be between 1 - Number of Stations This issue only happens with FSUIPC enabled, if you disable fsuipc then P3D no longer complains about a Payload station indexes error. However I rely on fsuipc for my control input assignments so I cannot disable it. We already posted this at LM support page. http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=125545 LM has now marked the post as [Resolved] because removing FSUIPC from the equation resolves the issue, so in retrospect LM thinks the problem is related to FSUIPC. This error happens on All aircraft, default and addons.
  4. Hi Dick, Did you ensure to remove all the key assignments you made at FSUIPC, from FSX generic button and axis assignments in the simulator, or else the combination of possible assignment of different function to buttons, axis, key strokes between fsuipc and FSX could clash.
  5. I just installed the 747-400 build 8334 via the PMDG Operations Centre and it fixed the "dead" issue with fsuipc 5.101k. All is working again. From PMDG OP Centre Change-log: PMDG 747-400 Queen of the Skies II - Build 3.00.8334 (Released 2017-06-09) [ View Issues ] ================================================================== - VARIOUS: [General] - Various non specific fixes. - VARIOUS: [General] - Temporary disablement of Squawkbox/IVAP/FSUIPC interface within 747-400 in Prepar3D v4 to prevent failure mode.
  6. Hi Pete, Just installed 5.101k and now PMDG 744 does not Initialize anymore, no landing gear, all gauges are dead, VC is "frozen" no buttons, switches.....reacts. When PMDG aircraft loads there is the green bar counting down the initialization process, It is just all dead now. Installed 5.101j and everything works again. 5.101k seems to totally "Kill" PMDG 744 Win10 Creators Update. FSUIPC5.log FSUIPC5.ini
  7. Hi Adrian, Dovetail in there twitch broadcast a week ago categorically said they will not and have no interest for/to having FSUIPC in there simulator or compatibility. They said they will and want to do everything themselves using "simconnect" Hardware developers and software developers must use "simconnect" to interact with there sim. Here is the twitchtv broadcast. https://www.twitch.tv/videos/141791355
  8. Thanks Pete for the information, I got it working now and no more error codes. All I had to do was select at least 1 of the cores that form part of the main Process in this case P3D. So P3D is set to use cores 2-3-4-5, AM=340 (No Hyper threads used) I set FSUIPC to use cores + Hyper treads of 1-5-6, AM=3843 Jannie FSUIPC4.log
  9. Pete not sure I am using it correctly? I have a 6 core Intel 6850K CPU with Hyper threading Enabled. P3D.cfg is set to use AffinityMask=340 ( Binary = 101010100 ) So using processors 2,3,4,5 Logical cores only and not their Hyper Threads. For FSUIPC I want to use the 1st and 6th Core + Thread so I set fsuipc.ini as follows [General] ThreadAffinityMask=3075 [ Binary = 110000000011 ] And fsuipc changes it to xC03 But I get this error in the log: 1750 ### Failed to set FSUIPC general thread affinity mask to 3075 [xC03], Error = 87 What am I doing wrong?
  10. I am so glad Srdan "Kosta" narrowed down this issue. I have Intel 6850K @ 4.4GHz water cooled, 16GB DDR4 @ 2666MHz, with a NVidia GTX 1080 water cooled, Windows 10 1607, Samsung 950 Pro NVMe SSD for OS, Samsung 840 Pro SSD for Flight Simulator, and OCZ Vertex 4 SSD for all Flight Simulator Add-on's. Having installed only P3D 3.4.18 and fsuipc, I use fsuipc only to assign and calibrate my Yoke and rudder axis's and assign buttons and key strokes. (All axis and button shortcuts in P3D deleted) I am using a BenQ XL2420G monitor, it is equipped with a G-Sync module by default, so this eliminates every and all types of stutters, you only get butter smooth gaming. So I was noticing always this very annoying micro stutter/freeze/ripples that was very visible on the G-Sync monitor because everything was always smooth, but at this every 9-10 seconds came this micro ripple/stutter effect over the screen. After a long test process of elimination I narrowed it down to if I disabled fsuipc from running then all was perfectly smooth again. So I knew for a while now of this issue but I have never had the technical know how to test it like Srdan "Kosta" did in this thread. I now set the entry OOMCheck=No and low and behold, everything is back to butter smooth flying as if fsuipc was disabled. Just a huge thank you to Srdan and Pete for discovering the culprit. Cheers, Jannie
  11. Get 4.921 from http://forum.simflight.com/topic/66139-updated-modules/
  12. Hi Pete, Just some feedback, I have just finished a flight of nearly 14 hours and confirm this as fixed now using 4.92a. I also noticed now that 4.921 is available. Just out of interest, what was the reason or the cause of this crash with Win8.1? Cheers Jannie EDIT: aah not to worry, I just read the pdf file that came with the download, I wonder what rogue data this could be.
  13. Hi Pete, Thanks for coming back about this. Unfortunately I would not be able to test this due to the nature of my work, Windows 8.1 and its issues are now on the back burner and will be revisited at a later stage. For the moment I am continuing work on Windows 7. When I get back to testing on Win8.1 and still experience crash issues at that stage I will return to this post with comments on the then current released version of FSUIPC4. Jannie PS. just so you know, no AI was used in any form, all default AI was turned off/disabled and no 3rd party AI was used.
  14. This time I was using FSX default built in weather, so that eliminate my FSGWX theory. fsuipc_crash.txt
  15. Hi Pete, I tried with 4.9.2 but still got the crash. This is sort of random, sometimes it is 40+ minutes into flight, other times only a few minutes. Sometime I am busy with the controls of the aircraft, other times it is just cruising not touching anything. So far I could not pin point what action triggers is. I am still eliminating stuff, next will try to not use FS Global WX to see if that could be the problem. Txt file contains all the usual details. fsuipc_crash.txt
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.