Are you referring to disabling roads and cars when using just ortho4xp i assume? Is there a trick to doing that outside of using the w2xp versions that are stripped down without roads?

 

No trick, I just don't generate roads with my scenery as not a fan of them, but I do add the streetlights.

 

 

 

What general area is this shot from.. very nice shot

 

It's near to EPZG Poland

Fps wise , i feel i may have lost around 2-3 , i have to switch off shadows and that gets me around 7-8 fps and then just OC the GPU to it's actual speed and again a boost of 2-3 fps.  So overall with Z16 18-21 fps and pretty much flyable. 

 

But would a 11kt x-wind really yaw the 172  hard to the left while on the take off run ?  I have to give full right yaw to counter it. 

 

Back to climbing to FL600 

No trick, I just don't generate roads with my scenery as not a fan of them, but I do add the streetlights.

 

 

 

 

It's near to EPZG Poland

When you say you dont generate the roads, is this an option somewhere in Ortho4XP, or does this involve using advanced tools such as WED, or i think i read, creating exclusion zones (unsure on this one as well)... can you point me to a reference as to how I would go about doing that, thanks

Fps wise , i feel i may have lost around 2-3 , i have to switch off shadows and that gets me around 7-8 fps and then just OC the GPU to it's actual speed and again a boost of 2-3 fps.  So overall with Z16 18-21 fps and pretty much flyable. 

 

But would a 11kt x-wind really yaw the 172  hard to the left while on the take off run ?  I have to give full right yaw to counter it. 

 

Back to climbing to FL600 

Sounds as though we experienced about the same performance difference.. wondering that about a 172 and the crosswind myself too...

When you say you dont generate the roads, is this an option somewhere in Ortho4XP, or does this involve using advanced tools such as WED, or i think i read, creating exclusion zones (unsure on this one as well)... can you point me to a reference as to how I would go about doing that, thanks

Sounds as though we experienced about the same performance difference.. wondering that about a 172 and the crosswind myself too...

 

Hmm Ortho4XP doesn't generate roads ? do you mean the overlay ? It you mean the overlay i doubt there is anything you could to do for removing the roads. 

 

ya it feels a little to hard on the yaw , but i can't say if it's realistic as i have no real world experience. I wonder how the tail draggers will behave now. Have to try the G6 with x-wind.

What is surprising to me is that , there is no fps increase when i just look up at the sky, don't know why though, a few times i found a very funny thing was the difference in fps when looking up at the sky in India and the sky above San Francisco have the same atmospheric conditions , what i noticed was i got more fps in the Indian skies then at San Francisco. They really need to optimize the rendering which i feel yield better performance results. 

 

Right now the CPU load is almost 100% .

No, the overlay is a custom scenery I made with W2XP where I don't generate roads. The photoscenery is a separate layer

BTW anyone tried the default S-76 or any other payware helis like the AS350 ?  any changes in settling with power ? 

I find that on my HDTV 55" I can fly in the minimum windowed mode and still have a 28"-32" picture but I double my FPS, so maybe I can live with it.

 

The S-76 performed fine for me.

 

If I come down on my settings some I can easily stay over 30 FPS, and even 40-50 FPS even with full screen., but I do love eye candy as much as I do the flying.

 

I may have to go to Fry's eventually and gift myself with a 28" monitor at some point, they have daily deals that actually last two days, back to back, always awesome finds, but you have to be subscribed to get the emails.

 

I have gotten awesome deals.

 

I think you can get a 24" 1080 monitor at least 2-4 days a week for around $100.

Wow these threads are moving incredibly quickly. Almost 100 replies and it's not even 24 hours old.

I tested out Beta 6 last evening, using the default scenery and with AIPilot's Mesh v3.  I also only flew the default C172SP and for weather, I used XP's weather download, with my customized Lua script.

 

- Lua works, though the "Lua has stopped!" message still appears, my scripts do load and run on initial startup.  The message could be tied to the latest release of Lua and I will wait for confirmation from the org forum.

-C172 idle sped has decreased to a manageable rate (~800rpm) so after releasing the parking brake, the aircraft can be controlled better, however the aircraft's tendancy to pull to the left or the right varies during taxi and rollout.

-C172 landing light switch now does not operate (filed a bug report on that)

-Frames are better than Beta 5, though I see a pattern of frames starting low on the ground, increasing in the air, and then decreasing on approach and landing which seems consistent with what would occur in the past.

-Since the first flight was with default scenery, and perhaps I'd been spoiled with the HD Mesh in the past, I found several areas around LA that the mesh has anomalies.  My second test flight with AIPilot's Mesh loaded fine and everything looked good.  Frame differentials between the two sceneries were marginal if not the same.

-Trailing black exhaust issue appears to be toned down.  In Beta 6, I still see the exhaust, but very slight and this could be due to my environmental changes, or they could have fixed the exhaust to be minimal.  I did not file any bug report on it, because I am not sure if this will be an intentional addition to XP11.

-Overall control of the C172, on the ground appears to be a little more challenging, similar to Beta 1 and 2, but for in the air, the aircraft handles the same.

-The map works better than Beta 5.  In Beta 5, there were serious issues with scrolling and zooming, but that appears to be taken care of now and I do see that on initial appearance, your aircraft defaults to a yellow "active" color.

-Flashing in cockpit is gone, and after bumping up reflections beyond minimal, flashing doesn't appear, though the "shaking" ground still appears, as well as the graininess, and that too only appears on the ground.

-Real weather depiction appears to be better.  I say "appears" because during my initial and second flight, I took off from KPDX (with MisterX6's KPDX scenery), and there were low-lying clouds and some haze, which the haze itself looks much more realistic and the transition from the haze into the clouds is blended, rather than a hard line differentiating between the layers.  Perhaps this is a subtle upgrade to indicate that the team is now actively working on weather.

 

This is about all I can personally report right now, but I will test further.  I hope my assessments help.

Lua works, though the "Lua has stopped!" message still appears, my scripts do load and run on initial startup. The message could be tied to the latest release of Lua

 

Please don't get me wrong, but let me add the remark that the term "Lua" alone is just referring to the programming language. I assume you are talking of "Fly with Lua", although in the past people even meant RealTerraHaze when using the term Lua.

 

Why is this important? Because a lot of plugins use Lua: FlyWithLua, SASL, Gizmo, X-Plane 11's own xLua. A general statement like "Lua works" could invoke the impression as if there were worries that none of these plugins would work.

Anyone noticing the 172 morse code is still off ?  

I have already filed it along with a couple of other issues like the mouse look and i am still losing fps after a while.

Have you tried turning the AI off? I had the same issue in b5 (fps steadily decreasing from a nice 50fps to 20 fps after an hour of flying). Threaded optimization was already off in control panel. On the dev blog, someone mentioned the problem in the comments and then someone suggested it was the AI aircraft and since I disabled all AI aircraft, I was able to maintain stable fps. Haven't tried b6 yet though.

They really need to optimize the rendering which i feel yield better performance results.

 

It's still beta. Final optimization won't happen until just before release. Beta software tends to have a lot of internal checks that creates overhead, and these error checking routines don't get removed until the code is finalized. Which is to say that beta software is inherently unoptimized as a general rule.

pb6 freezes the view if you use two monitors, and the second monitor has the popup map or GPS. Too bad...

I have the same problem. Have filed a bug.

 

cheers

Peter

Some claim that XP is always in Beta, but the question is, when will there be a final version for a DVD release?

 

Is it after all those known bugs are fixed? I doubt that all those bugs will be fixed by the end of this month. :smile: