Comments on: Dude, Where’s My Taxiway?

By: Ralph Wigzell (Raffles)

Ralph Wigzell (Raffles) — Sun, 12 Oct 2014 08:28:43 +0000

In reply to Ben Supnik. It will be much appreciated :)

By: Ben Supnik

Ben Supnik — Sun, 12 Oct 2014 03:10:26 +0000

First, if the tech press stuff is correct, you can go turn on DSR without app intervention. We’re certainly not planning to do anything to support it.

And…from what i can tell, DSR isn’t a whole lot different from what we do with 4x SSAA in HDR mode. I would expect the performance hit would also be almost exactly the same; the technical description of DRS I found is “render the image bigger and down-size” – that’s exactly what HDR SSAA does. (In nerd lingo, our SSAA is called OGSSAA for ‘ordered grid’, which just means the sub-sample points aren’t rotated).

So my expectation is: you won’t get better speed. You might get better performance; for example, their down sampling filter might be better tuned. But this is just a small fraction of the cost of the anti-aliasing.

By: Oscar

Oscar — Sat, 11 Oct 2014 21:00:34 +0000

That’s the kind of answer I was hoping to hear… so it’s likely just a mistake, not a choice XD

By: Gal Cohen

Gal Cohen — Sat, 11 Oct 2014 19:03:10 +0000

Hey Ben,
sorry that this post is a bit out of topic … 🙂
I assume that you did see the Dynamic Super Resolution that Nvidia published with the new drivers for the 900 series , and it’ll follow for the 600 and 700 series in the next drivers I think.
As I understood it works almost like SSAA that is in XP , while it’s more gentle on performance.
I didn’t try it myself because I have and old GTX 460 , but do you think that it’s possible that as a user I can run lower AA in XP while DSR is on , and get basicly the same result with higher perforamnce , that let’s say 4XSSAA + FXAA?
And mainly , should it work with XP or you , the developers will need to do some code stuff in order to take advantage on that ?

By: Ben Supnik

Ben Supnik — Sat, 11 Oct 2014 15:40:38 +0000

In reply to Ralph Wigzell (Raffles). This is why I think we need an auto-checker in WED - it's really really really hard to find these errors by hand!!

By: Ralph Wigzell (Raffles)

Ralph Wigzell (Raffles) — Fri, 10 Oct 2014 19:57:32 +0000

In reply to Ben Supnik.

Hi Ben, I found the error after 2 days of searching with a fine toothcomb using WED. It was indeed an overlap. The scenery came from FS2004 and was probably converted using a conversion tool. I had a great learning curve. Your link above helped a lot.
thanks
Ralph

By: Ben Supnik

Ben Supnik — Thu, 09 Oct 2014 20:11:30 +0000

In reply to Rudy.

Others have responded to this more eloquently than I was going to…I was just going to write something snarky like “don’t fix bugs in other people’s features, implement MY feature!”. 🙂

I do agree that the bezier S curve bug was a small one and people want visibility badly. But the result of the S-curve bug is a major regression bug in 1030, so now it’s important.

By: Ben Supnik

Ben Supnik — Thu, 09 Oct 2014 20:10:26 +0000

In reply to Oscar. That is weird that it is in markings-1 and not taxiways or something...

By: Ben Supnik

Ben Supnik — Thu, 09 Oct 2014 20:09:44 +0000

In reply to Ralph Wigzell (Raffles).

I’ll try to post one next time I have one open in WED.

This link is super-old but has a few pics of fubar beziers:

http://scenery.x-plane.com/library.php?doc=apt_guidelines.php

By: Oscar

Oscar — Thu, 09 Oct 2014 17:54:14 +0000

Ben, on a related note:

I’ve given the X-Plane library’s custom pavement a try, wanted to use some asphalt for runway shoulders and such, but I noticed that all custom pavement is in layer group ‘markings -1’, which kind of seems to negate the flexibility the layer system was designed for in the first place 😉

Would it be possible to put them in a layer group between taxiways and runways, e.g. ‘taxiways +3’ or ‘runways -3/-4?’
I realize this will affect airports that rely on the current layering, but I doubt that it will be many…

anyway, I like the WED validating stuff 🙂