[FPS after update]

On low light (dusk) I noticed also stuttering now, reduced fps, especially when I was taxiing, was not the case before SP1. 

[Ejets installed outside of P3D will not appear]

For the pre SP1 release I added manually the lines below in the add-ons.cfg, you may try that. I also did not use the P3D folder but my add-ons custom folder.

[Package.xx]   <- depends by your list
PATH=F:\Lockheed Martin\Prepar3Dv4_Addons\FeelThere EJets  <-depends to your path
ACTIVE=true
REQUIRED=false

On my side the installer, ran as admin did not see the module/add-on so I did it manually.

For SP1 might be the same issue but I did not install it yet.

[SP STATUS]

2 minutes ago, Matty260191 said:

its in the known issues thread

Thanks for the heads up, I did not check that as by edit is not marked as something new 😄

[SP STATUS]

Sounds like good news. Do you have a list of items which will be included in this SP which can be shared with us in advance of the release? 

[Repaints - Requests and New Releases]

Guys, do you know if there is an E175 livery for KLM? On avsim or iniBuilds I could find for E190 only for now.

[Service Pack question]

I am wondering if the list of know problems can be updated in the respective post, in that way will be more clear for the people what is acknowledged (and perhaps will be fixed) and what could be a new bug. I think the last update is from 17th of December. Just an idea.

edit: I see some updates, just not sure if it is the latest status.

[APU message on EICAS]

I noticed that after the second engine is starting (first engine already is started) the message "BLEED APU VLV OPEN" disappears from EICAS which I saw in a movie that it does not, till the APU is turned OFF. I realized this because I forgot to shut the APU off and I found that in flight.. As long as that message stays on EICAS is a reminder that it has to be turned off. 

(After start, if you turn OFF left engine the message appears, if you turn OFF only the right engine it does not. I suppose the logic is implemented depending by engine 1 condition. In the video below it does not seem to depend). Can this be checked (or perhaps is explainable)?

 

[Flight plan question]

The initial flight plan is:

EDDM KIRDI3W KIRDI DCT MEDEL DCT STEIN DCT NARKA Z650 ATSOS ATSOS1X LRCL

Controler gave me KIRDI3S departure. You can see after update, from KIRDI to ATSOS the waypoints are missing.

Video here:

 

[Flight plan question]

One question regarding the flight plan, why when I change the departure or the arrival I loose all the intermediate flight plan waypoints?

The VATSIM controller can give me a different departure or arrival and when I change I see that I loose also the waypoints already programmed between the departure or arrival or between where I am and arrival. Is this normal?

[Slow loading textures]

Yes, they are slow in loading, in my opinion the VC textures and its lighting implementation should be optimized and improved more by the team. Probably to use implementations like the other are doing nowadays.

[Repaints - Requests and New Releases]

6 hours ago, tayibetom said:

Would there be any chance of an airfrance HOP! for the 190?

 A HOP! livery for E190 was uploaded to Avsim by Miguel Angel Taboada:

https://library.avsim.net/download.php?DLID=215736

 

[MERRY CHRISTMAS]

Merry Christmas to the Feelthere team, looking forward for nice updates in the new year  🙂

 

[Repaints - Requests and New Releases]

3 hours ago, espresso said:

Another request has been fulfilled!

Austrian E195 OE-LWA

https://drive.google.com/open?id=1RCfSHubKxMx5jfpPXCVQe_T3n83FNqt3

 

Great one, thanks!! 🙂 I really like it, nicely done! 

Hopefully an Air Dolomiti for E915 will be made also sometime.

[TCAS (E175) not working on Vatsim]

You can set vPilot to automatically switch to mode C at departure, in case you forget to switch it manually, but yes, it will be nice to be coded into the FeelThere product itself.

[Panels night texture issue - night lighting v. floodlights]

5 hours ago, antoniointini said:

Dome light here.

Also, yes.

[Embraer E170/190 V3 Install into Add-On folder]

On my side, I added following to add-ons.cfg and it worked (replace xx with the appropriate number on yours and also at the PATH use your installation path):

[Package.xx]
PATH=F:\Lockheed Martin\Prepar3Dv4_Addons\FeelThere EJets
ACTIVE=true
REQUIRED=false

 

(add-ons.cfg is on my PC at C:\Users\All Users\Lockheed Martin\Prepar3D v4)

[Panels night texture issue - night lighting v. floodlights]

From the Chart light for me also.

[APP in HDG mode]

4 hours ago, FeelThere said:

We appreciate your reply and especially your professional attitude.

Happy holidays

 

Vic

Hello Vic,

Thanks for the kind words, happy holidays too!

I did the flight again, this time I've updated also the AIRAC from Navigraph to the actual cycle.

Flight plan was: EDDM KIRDI3S KIRDI DCT MEDEL DCT STEIN DCT NARKA Z650 ATSOS ATSOS1E LRCL and then on cruise I switched to ATSOS1F (so from initial planned rwy 07 to the rwy 25, this I did also last time).

Some notes:

1. when I planned the flight I noticed that one waypoint was at 1890nm from the previous one , this was automatically so inserted during selection of the arrival. I noticed that, after I deleted that waypoint and when I manually introduced it, was then fine. Look at AXUTA in the screenshot:

 

2. After AXUTA was corrected, the radial (282 degrees to intercept, D282I) was far away, see the screenshot below (the FL I corrected manually based on charts afterwards):

 

3. The problem this time was after EBILO at the radial intercept, see the screenshot below, it goes right ignoring LNAV (and also I attached the FLT files, e195_002 are before the waypoint, e195_003 are after turning).

https://drive.google.com/open?id=1su317t6SSWfT5ObON1zQbJMu58D3dTeo

Perhaps is something wrong with the definition.

 

4. I switched then to HDG mode, to do the arrival manually,  then to V/L and APP and this time this was OK, landed in good conditions.

[APP in HDG mode]

Yesterday I did some tests by doing patterns at EDDM, with LNAV mode (FMS1) to switch to LOC/GS and also with HDG mode to switch to LOC/GS (using V/L and radio NAV) and both were OK, I need to redo that trouble flight to see if it happens again. If yes, I will come back with the .flt file.  I need to be sure that it was also not a mistake on my side.

[APP in HDG mode]

8 minutes ago, FeelThere said:

Please post an FLT file right when it happens so we can re-create it.

 

Thank you

 

Vic

I will do more flights and if it will happen again will post the FLT file.

(The flight plane where I had issues was EDDM KIRDI2E KIRDI DCT MEDEL DCT STEIN DCT NARKA Z650 ATSOS ATSOS1F LRCL, ILS rwy 25)

At EBILO the E195 lost also the LNAV, it made a wrong turn.

 

[APP in HDG mode]

I had an issue too.

I was using HDG, then switched to V/L, LOC1 with green was displayed on the bottom of the PFD (HSI), ILS freq and course was set by me OK, but when  I pressed the APP HDG was blinking and LNAV was under HDG, no LOC/GS mode... I landed using the green dots for ILS in the end...but I could not arm the LOC/GS, only LNAV was displayed under HDG even if I pressed V/L.

[Repaints - Requests and New Releases]

inibuild LH is looking good, only on the right engine the writing is backwards (mirroring of the left engine probably)

[Overhead button light issue]

I had the same thing, after I load the plane again, was OK.

[Front landing gear]

This is the E195 but I noticed the same for the E175.  I do not own the 170/190.

[Repaints - Requests and New Releases]

I would say Lufthansa and Air Dolomiti 😄 (195)