Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Skipy33

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This problem with all Feelthere products was introduced with P3D4.2 release. I was suspecting a Logitech wireless mouse driver compatibility issue but I still have the problem with a classical wired mouse. Today I'm flying P3D4.5 and this problem makes me feel that I'm using a low end computer with FPS fluctuations down to 15 where any other addon including TFDi 717 or PMDG 747-8 are running very smoothly. I hope the new E-jets will use another source code.... Skip.
  2. Mouse M560 wireless but the keyboard is wired. In fact it's the USB wireless plug-in which is the source of the problem I think. Just remove it and FPS become steady.
  3. Hi Fernando, I have almost all available good addon aircrafts on P3D4 and Feelthere ones are the only one where I have a real problem with FPS stuttering. AS CRJ and Airbus are in my opinion not concerned. I remember that the problem appeared on Feellthere after the P3D upgrade from 4.1 to 4.2. But now that now you found that only users with some Logitech mouses (and keyboards?) are concerned by this issue, I'm afraid that Feelthere won't investigate on this as they already wrote here. My concern I'll use another mouse during Feelthere aircraft flights and that's all. The strange thing is that my Logitech keyboard does not create any issue. Skip.
  4. I'm flying the E145XR right now and no more FPS stuttering problem just by unplugging my Logitech M560 USB receiver and using a HP wired mouse instead. By the way I found in the Feelthere documentation that "mouse butons and wheel are used to control the panel and 3rd parties mouse applications could have to be tuned....". In Logitech case it seems that there's no tuning to solve the conflict. Skip.
  5. Fernando, This sounds very interesting because I also use logitech Mouse + Keyboard!!! I tried to change many parameters in Logitech control panel but without solving the issue. Uninstalling Logitech drivers is not a solution as all other addons are working well and I need some specific features that SetPoint gives. Perhaps Feelthere will have an idea about the conflict source? Skip.
  6. Hi John, It's fixed with this new DLL. Thank you very much. Skip.
  7. John, I confirm I'm using FSUIPC5.15 and here are the outputs of a little test I just made: - P3D4.4 startup with correct unique macro file (MACROS - Before.MCRO attached) - After loading an aircraft I just added a new macro to MACROS (ERJ_NDMODE) - Just after ending the mouse macro session the saved file is corrupted but the new macro is there (MACROS - After.MCRO attached) I also attached the log of this session. Regards, Skip. FSUIPC5.log MACROS - After.MCRO MACROS - Before.MCRO
  8. Hi John, I'll double check this evening at home in case some addon installed an older version silently but I'm pretty sure it's the 5.15 I'm using. If you want my macro file to make a test just let me know. Skip.
  9. Hi, With P3D4.4 mouse macros are working great and it's a very good thing after waiting so long. But I discovered today I have a bug with macro file recording which is similar to the one we had with the first FSUIPC5 version supporting mouse macros (entries are truncated). In fact it's not exactly the same thing as the bug affects only "sub entries" of my single macro file. Here's an extract of my file MACROS.MCRO I'm using for several aircraft: [Macros] 1=MD82_TERR=RX400000a9,3 2=AV_TMSTO=RX2040f805,3 3=AV_TMSCR=RX2040f806,3 4=AV_TMSCL=RX2040f807,3 5=AV_FLCHG=RX20413000,3 6=AV_VS=RX20412800,3 7=AV_LOC=RX20414800,3 ..... 32=BA_FMSPWR 32.1=RX2080d004,3 32.2=RX400000c1,3 33=BA_LNAV=RX2040c800,3 34=BA_STA=RX2080c806,3 35=BA_APT=RX2080c807,3 36=BA_WPT=RX2080c808,3 37=BA_TCASON=RX40000048,1 38=BA_TCASOFF=RX40000048,3 39=BA_RWYLTS=RX40000036,3 40=ERJ_AVIO 40.1=RX2080000c,3 40.2=RX2080000d,3 40.3=RX20800041,3 40.4=RX20800042,3 41=ERJ_STORE=RX20800053,3 ...... Since I have set macros with multiple entries (in bold above), these lines are corrupted as soon as I'm adding a new macro. All the other entries stay good. If I'm updating one of these multiple entries macro (ERJ_AVIO for example), all existing sub entries are corrupted except the one I just added. Hopefully I keep an up to date copy of my macro file elsewhere so I can restore the corrupted lines each time I'm updating this file with new macros but if you can solve the problem it would be great. Thanks, Skip.
  10. The problem that appears since the P3D4.2 upgrade and next versions is that the FPS on all Feelthere aircraft (170,175,190,195,135,145XR) is fluctuating by 100% without any reason. This happens as soon as the plane is loaded in a cold and dark state, without anything moving around and even at a standard "simple" P3D4 airport. With any other aircraft including PMDG, Aerosoft, Maddog, TFDi, CaptainSim.... when I'm in the same situation I get a steady FPS (usually the FPS limit = 40 I gave) on a standard "simple" P3D airport. With Feelthere ones, FPS is fluctuating from 40 down to 20 approximately every second. I have now a i7 8700K@4.8GHz with a GeForce 2080 RTX and my opinion is this is not a normal behaviour for this addon. With P3D4.1 170/190 aircrafts were running very well. It's perhaps a conflict with another addon (ASP3D4, FSUIPC5, ....) but in this case Feelthere products are the only one to have this issue. PS: The "fluctuating FPS" issue is also happening when the sim is paused.... Skip.
  11. Hi, If there's a conflict with another program it seems that I've reinstalled it on my new computer. But I remember the issue happened after moving from P4D4.1 to 4.2. Before all was running very well and it's the reason why I was suspecting a problem with simconnect because FSUIPC5 had the same issue. By the way by debugging version I mean more debug info in the log file (enclosed) after loading. As far as I can see there's no problem with loading the aircraft. Skip. e170.log
  12. Hi, The "local computer issue" could be a reason (Windows DirectX version, Nvidia drivers & Inspector settings....). But now I'm running a new install of P3D4.4 on a new "boosted" computer and the problem is still there. Using P3D FPS limiter set to 40 I can see the FPS switching from 40 to 24 every second. By "local" you mean geographical position? ;-). Is it possible to get debugging version of the gauge to find where is the issue? Skip.
  13. Hello, I'm sure I already made a test long time ago with '0' for all FPS values with the same result but here are the current settings: ERJ: [FPS] pfd=100 mfd=66 eicas=66 rmu=36 isi=70 fms=34 hud=100 E170: [FPS] pfd=80 mfd=46 eicas=46 isi=47 fms=50 Even when cold and dark FPS settings can have an effect on the sim? Regards, Skip.
  14. Hello, I've just installed the latest releases of your products in my P3D4.3: - ejetsv2-p3dv4-3 - ejetsv1-p3dv4-3 - erj135-145xr-p3dv4-2 I still have the same problem. Test made at Key West airport (cold and dark, no AI aircraft) and FPS value is moving from 24 to 40. If I change vehicle to Aerosoft A318 Pro for example FPS are almost steady at 30 (NVidia Inspector FPS limiter value). This means that in a more complex environment (large airport, AI traffic and complex weather) FPS can move from 8 to 24 which is very annoying. Skip
  15. Hi, When I ran for the first time the ERJ 135 on P3D4.2, I can't see any nav lights or beacon lights except the white one. I check the aircraft.cfg and light entries were correct but I can't find the associated .fx files in P3D4\effects folder? I copied the .fx files and textures from my FSX installation and lights are now OK in P3D4 (but flashing too fast...). Is it an installer bug? Skip.
  • 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.