Thanks for the video Rob...exciting stuff!

Thanks for the insight Rob, thank you beta team for helping improve my sim, and now I must, simply...

 

shut up and fly.

And all the vids he has made to show things .

 

Took out your iFly 737 for a spin ... I don't have many hours in this aircraft (only about 8 total) so I'm not that familiar with all the systems ... just ran a basic check and everything seems to be working well.  The taxi light sometimes don't illuminate the taxi way.  Other than that it seems to be working well.

 

 

Cheers, Rob.

 

EDIT: If there is anything specific in the iFly 737 you want me to test let me know - can't promise I'll have the time, but I'll take note. 

Many thanks Rob !

Very nice vid and beautifull flight.

 

This is what Flight1 says about Nav light issues in v2.3 and 2.4. I am curious if they still exist in v2.5 :

 

- The white/green/red wing nav lights don’t always activate correctly.

- If the sim is started in night time then they work fine.

- P3Dv2 introduced a bug that prevents NAV lights to work correctly in some situations.

Here is a workaround: First fully load-up/start with a default P3Dv2 aircraft at the gate/stand or runway, then switch and load your iFly aircraft.Then all NAV lights work any time of day.

 

Thanks,

Gerard

When we were testing the MS-FS series, starting from FS4, we were often joking, saying that often we have fours times more accumulated SLEW time, than we did actual flying... You simply need to know HOW to test stuff, how to find out in a single minute if clouds are rotating or not, if oversized clouds cause 50% performance loss and the like.

 

Do not take it personally Rob, there's nothing against you in my sentences.

Most probably it is the entire beta-system which needs a fairly strong refurbishment at LM.

 

There are many valid ways to beta-test. If everyone was using slew mode all the time, other issues would go undiscovered. So simply using the sim as a normal user is valuable too.

 

However slew mode can be a very useful tool for stress-testing the rendering engine, to discover things like the OOM's in v2.1 that forced everyone to run that version with vegetation Autogen turned off. That issue was at its most severe when moving rapidly over the landscape, partially because the scenery engine couldn't keep up and wasn't unloading tiles fast enough.

 

Some beta testers need to focus on particular subsystems - e.g. "Today I'm going to check how the cloud rendering behaves under all sorts of normal and extreme conditions. I will use slew to rotate quickly and slowly along all axes, add cloud layers at extremely high and extremely low altitudes, slew through the cloud cover at extremely high speeds, then at very low speeds, at day, at dawn, at night... etc. etc.". Another day, maybe you focus on water rendering, or physics, or make sure all the dialog options do what they're supposed to (remember the IFROnly bug in P3D 1.4?).

 

Of course all the beta testing in the world won't help if the developers aren't taking the input into account, or aren't prioritizing bugs that the beta team reports. This may very well be where the problem lies. The troubled v2.x cycle so far definitely indicates that something is amiss.

P3Dv2 introduced a bug that prevents NAV lights to work correctly in some situations.

 

I'm not sure it's a "bug" ... as I understand it the P3D lights don't render the same way as in FSX ... if you look at Aerosoft's Airbus for P3D, you can see how well the nav lights work there and even light up the ground/surroundings.

 

In the video I made of the iFly 737, I can't see the green nav light but could be on the other side, the red and white don't illuminate much (perhaps by design).

 

Here is Aerosoft's Airbus with working nav lights landing at the same location -- fast forward to 17:00 mark: 

 

 

So it can be done, it's just done a little differently in P3D.  I'll check out day/night ... I recall the CS 777 early versions having a similiar issue, but they resolved that with v1.5 or was in v1.6 of the 777.

 

Cheers, Rob.

 

 

Wake and Rotor wash over water that has wave animations looks a little odd but my hunch this is a compromise we'll have to live with.

Hi Rob,

that's good news for the heli users. Thanks for sharing this information.

Spirit

Of course all the beta testing in the world won't help if the developers aren't taking the input into account, or aren't prioritizing bugs that the beta team reports. This may very well be where the problem lies. The troubled v2.x cycle so far definitely indicates that something is amiss.

 

The developer will prioritise  reported bugs which also means low priority bugs will not be dealt with immediately. If the developer doesn't hink they are significant, or  are too complex to fix,  then they may never be  dealt with. Developers don't have unlimited budgets and concentrate their available resources.

 

One  developer got rid of such  bugs  by calling them PSRs - Permanent Software Restrictions.

Wow, what a thread...

 

All I know is that Prepar3D v2.4 works very well on my computer. Low level flights in fighter jets with max autogen and no autogen popping or blurries is a first for me in FSX/ESP/P3D-history (No, I didn't test it over NYC).

 

Sure, there are several issues to be fixed, but considering what LM has done up to this point, most of these bugs are minor.

 

At this point in time the only nits I have with v2.4 are occational stutters (I live with it because I know I'm pushing my hardware to the max), occasional flat clouds (spoiler, but hey, I remeber FS5 clouds) and broken wakes from ships (the wakes are a bit excessive anyway).

 

All the other bugs people are whining about hasn't spoiled my fun in any way, but then again, I only use a very limited few dedicated P3D addons.

 

Thanks Rob for your reports. It's fun to be kept in the loop.

 The 1/2 refresh rate vsync is a must to get working.

 

Not sure who this lies with, Nvidia or LM but its the last thing left for me to ditch FSX totally. 

 The 1/2 refresh rate vsync is a must to get working.

 

Not sure who this lies with, Nvidia or LM but its the last thing left for me to ditch FSX totally. 

 

I use one of the card manufacturers supplied software apps to lock the video card output at 30 and set P3D to unlimited.

 

I use Asus GPU Tweak but I know there are other similar apps about.

I use one of the card manufacturers supplied software apps to lock the video card output at 30 and set P3D to unlimited.

 

I use Asus GPU Tweak but I know there are other similar apps about.

 

Thats not the same thing though.

How many of you get the "vertical contrails" in P3D v2.4?

Thats not the same thing though.

 

Is it not? My mistake.

 

What's the difference between the two methods?

Chris,

 

The only issue with contrails I've noticed is where the extrudes draw at varying altitudes and thusly give a "double contrail" effect. A video can illustrates this much better than I can describe it and the same is probably true for a "vertical contrail" effect if it is something different than what I've described.

 

From Rob's videos and LM's communication, there has definitely been work on extrude effects but not sure if contrails have been fixed.