[MakeRwys 5.11 and new ORBX/MK-Studios LPPD Ponta Delgada addon path]

Hi Pete,

Yes it's because 5.11 was written that I didn't try to download Makerwys again :-).

I've made the test with 5.126 with the same result (I'm using Notepad++ to view/edit xml files).

Adding encoding <?xml version="1.0" encoding="Windows-1252"?> in runways.xml header fixed the problem with Super Traffic Board scenery scan :-). 

Regards, Skip.

[MakeRwys 5.11 and new ORBX/MK-Studios LPPD Ponta Delgada addon path]

Hi,

I've noticed that Makerwys 5.11 does not like Portuguese special character used in the folder name of latest ORBX/MK-Studios LPPD addon.

In runways.txt all is OK:

Area.414 "Ponta Delgada" (Layer=414)
Path(Local/Remote)=L:\ORBX\p3dv5\LPPD Ponta Delgada - João Paulo II Airport\ORBX\MKStudios\MK_LPPD
=============================================================================
L:\ORBX\p3dv5\LPPD Ponta Delgada - João Paulo II Airport\ORBX\MKStudios\MK_LPPD\scenery\LPPD_ADEP4_MK.bgl
=============================================================================

But in runways.xml the 'ã' is coded 'xE3':

<ICAO id="LPPD">
<ICAOName>Joao Paulo Ii</ICAOName>
<Country>Portugal</Country>
<City>Ponta Delgada</City>
<File>L:\ORBX\p3dv5\LPPD Ponta Delgada - JoxE3Paulo II Airport\ORBX\MKStudios\MK_LPPD\scenery\LPPD_ADEP4_MK.bgl</File>

As a consequence some tools like Super Traffic Board are not able to read the path correctly. Of course it's easy to edit runways.xml to fix the problem each time Makerwys is executed but is there a way to change this?

Thanks, Skip.

[FSUIPC6/P3Dv5 - Runif kill and close statements trouble]

7 minutes ago, Pete Dowson said:

Thanks for letting us know.

Pete

 

You're welcome. After removing and reinstalling this ORBX package it's OK now.

Skip.

[FSUIPC6/P3Dv5 - Runif kill and close statements trouble]

55 minutes ago, Pete Dowson said:

Right. DLLStop is the procedure in FSUIPC (in all added SimConnect DLLs) which is called by the simulator when it is closing. without that notification FSUIPC cannot do any tidying up.

No, it isn't even getting the notification. I think your P3D5 is not closing but crashing out. Check the Windows Event Viewer to see if there are any errors listed mentioning Prepar3D.exe. They'll be in the Windows Logs/Application section.

Pete

 

Pete, you were right as always! I found a Kernelbase.dll crash exiting prepar3d. The fault is on ORBX objectflow addon and I'll now investigate with them.

Thanks for your help.

Skip.

[FSUIPC6/P3Dv5 - Runif kill and close statements trouble]

3 hours ago, Pete Dowson said:

Where's the log, please, showing this.as requested.

I'm taking a little time off now, so it'll be later -- enought time for you to find the log, for sure! 😉

Pete

 

 

Ok, here's the log. I've made the comparison with an old FSUIPC5 log and I can see that FSUIPC6 isn't closing properly. The last line is :

101984 === Closing session: waiting for DLLStop to be called ...

My P3D5 is still very "light" in terms of addons so it exits very fast. Is it possible that Prepare3d.exe is exiting so fast that FSUIPC6.dll doesn't have the time to finish the job?

Skip.

FSUIPC6.log

[FSUIPC6/P3Dv5 - Runif kill and close statements trouble]

Hum... The only difference was the "disable full screen optimization" not set in P3D5 (I remember I had to set this in P3D4 because I had issues with snapshots). I've just made the test with it and I've got the same result. P3D5 exits well (Chaseplane exits few seconds after) but the 3 programs launched by FSUIPC6 no:

[Programs]
Runif1=READY,HIDE,CLOSE,I:\P3Dtools\sadvX.exe
Runif2=KILL,I:\P3Dtools\Greenshot\Greenshot.exe
Runif3=READY,HIDE,CLOSE,I:\VRInsight\bin\SerialFP2.exe

Skip.

[FSUIPC6/P3Dv5 - Runif kill and close statements trouble]

Hi,

I've just upgraded to FSUIPC6 and now I'm using it for both P3D4 & 5 (separate installs but same settings, addon.xml method for both). With P3D5 it seems that the Kill or Close actions in Runif are not working. No problem with P3D4 (same behaviour than with FSUIPC5). 

Any idea of the cause?

Thanks. Skip.

[Stutters when handflying the E-jets in P3D 4.2]

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.

[E_Jets V2 and P3D4.2]

3 minutes ago, Fernando G said:

Well at least they should investigate what hardware make the stutters and should make  compatibility fix, this is an issue when playing fsx so hope they should give an answer, what mouse and keyboard will you use? My mouse and keyboard are wireless, is your keyboard wireless?

 

Fer

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.

[E_Jets V2 and P3D4.2]

25 minutes ago, Fernando G said:

Hello Skip,

Today I bough PMDG 737 and with defaul settings in P3D I get a constant of 50 FPS with Logitech and mouse and keyboard connected, so there something wrong in the EJET and ERJ module that tries to comunacite with some hardware or something like that because even disconnecting the keyboard and mouse I don’t know if it is your case but the FPS still make an instant peak down, can you confirm this with the FPS of the sim ? can you test it with another module you have just to make sure I’m not going crazy making the job of the feelthere engineers?

 

thanks Skip

Fer

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.

[E_Jets V2 and P3D4.2]

28 minutes ago, Fernando G said:

Hi Skip

Did you try unplugging the mouse and keyboard just to check  the FPS ? What I found is to unplug them to solve all the FPS issues.

Fer

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.

[E_Jets V2 and P3D4.2]

11 hours ago, Fernando G said:

Hello i did what scoob say, i adjusted the fps lines of the config utility but didnt work, did a reinstall of windows 10 an neither work, what i found that work was unpluging the mouse and keyboard, that fixed the stutters and give a boost to the fps even to 100 fps over water all this in fsx and p3d. What i discovered is that my mouse M570 and keyboard K220 are from logitech unpliging them gave me the solution i was looking for. The strange thing is that i connected an EASY line mouse and all went fine, no stutters and good fps, this make me think that your module is not compatible with logitech hardware, by the way this just happen only with your moudules EJETS V1, V2 and ERJ in fsx and p3d, i have DCS and IL2 and the planes included in FSX and P3D and no one of them gave me a problem.

Well thats what i found in a weekend of hard work trying to fix your module, i think that the developers  should had found the compatiblity issues of the modules in all the months we have been waiting for a solution of stutters, well i hope you can fix this out or tell us what hardware is compatible with your module. 

Thanks 

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.

[FSUIPC5.15 corrupted macro file]

45 minutes ago, John Dowson said:

Hi Skip,

can you try the following dll please - unzip and use to replace the one in you Modules folder:

FSUIPC5150e.zip

Cheers,

John

Hi John,

It's fixed with this new DLL. Thank you very much.

Skip.

[FSUIPC5.15 corrupted macro file]

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

[FSUIPC5.15 corrupted macro file]

6 minutes ago, John Dowson said:

BTW, what version of FSUIPC5 are you using? The latest (supported) version is 5.15.

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.

[FSUIPC5.15 corrupted macro file]

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.

 

[E_Jets V2 and P3D4.2]

6 hours ago, FeelThere Ariel said:

Skip, 

The problem you are refering too is the FPS issue right? If it is, there should be no problem loading the airplane. What I meant by "local issues" is that FPS may be affected by different programs installed or specifications in each individual computer. In this case, it almost comes down to each individual user to troubleshoot which program or computer spec is causing the issue.

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.

 

 

[E_Jets V2 and P3D4.2]

2 hours ago, FeelThere Ariel said:

By "local" I mean in isolated computers (individual computers). Each user has different programs running in the computer that may affect this. 

what do you mean by "debugging version"? 

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

[E_Jets V2 and P3D4.2]

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.

[E_Jets V2 and P3D4.2]

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.

 

[E_Jets V2 and P3D4.2]

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

[ERJ P3D4 lights effects are missing]

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.

[E_Jets V2 and P3D4.2]

2 hours ago, FeelThere said:

Skip,

If I understood you correctly with the other planes you get 30 fps and with ours 24-42. I can imagine it's annoying when you watch the fps on your screen however a complex plane such as ours would not raise a concern if you'd get a steady 24. 

 

Vic

The FPS I gave you are coming from a test situation: KEYW airport add-on, cold and dark state without weather engine or AI traffic moving on. I let you image how this "fluctuating performance issue" can impact the simulation in a very complex situation: Big airport add-on, hundreds of AI aircraft and Active Sky weather with rain at night with dynamic lightning activated.

I confirm that I have this behaviour only with your 3 Embraers products. With E-Jets v2 the issue arrived just after moving from P3Dv4.1 to P3Dv4.2. Perhaps on very powerful machines people don't notice the problem.

The fact that FPS can fluctuate from 24 to 45 instead of being caped by NVidia FPS limiter is the proof that something is wrong in P3D4 display engine.

Skip.

[E_Jets V2 and P3D4.2]

On 29/03/2018 at 12:09 PM, FeelThere said:

Our upcoming ERJ will require P3D4.2 and we will see if that solves any problems (by making it 4.2 compatible only). Based on the information we collected 4.2 is causing issues for other developers as well so we are still watching this problem.

 

Vic

 

Hello,

Exactly the same problem with ERJ 135/145XR for P3Dv4.2.

Skip.

[E_Jets V2 and P3D4.2]

7 hours ago, Sabrefly said:

Please let us know if you find a fix fo the FPS mess.

Thanks

No I didn't find any fix or workaround. Even without all dll's and exe modules (Active Sky, PMDG, FSUIPC,...) I have the same issue. I was able to perform a flight but it's very annoying and causing stutters. I'm still waiting for an official answer from feelthere who is working on it.