I like to think that I am the Buzzwinkle of Laminar Research…I’ve been around forever, I’m often sloshed, and you have to hit me pretty hard on the head to get me to move. 🙂

Great story SD

That’s part of what’s going on – the HDR AA other than FXAA is OGSSAA (ordered grid super sampling), which is fancy talk for just drawing things biiiig and scaling them down.

Whenever possible, the b14 code separates clouds from the main screen, escaping the costs of the size of the screen, anti-aliasing, etc. But there are some views where this cannot be done.

You should find that in some views, the penalty for 4x FSAA in HDR mode is much lower than it used to be with clouds – it was basically never useable with clouds.

take xjoymap, (bless you Joan,) create a .xjm file for your default aircraft

[Landing_Lights_On]
new_command=ex_lights/landing_lights
dataref=sim/cockpit2/switches/landing_lights_switch[0:16](float)
values=1

[Landing_Lights_Off]
new_command=ex_lights/landing_lights_off
dataref=sim/cockpit2/switches/landing_lights_switch[0:16](float)
values=0

now for some other aircraft

[a320_R_Landing_Lights]
new_command=ex_lights/landing_lights
dataref=sim/custom/xap/extlight/landr_sw
values=2

[a320_R_Landing_Lights_Off]
new_command=ex_lights/landing_lights_off
dataref=sim/custom/xap/extlight/landr_sw
values=1

[a320_L_Landing_Lights]
new_command=ex_lights/landing_lights
dataref=sim/custom/xap/extlight/landl_sw
values=2

[a320_L_Landing_Lights_Off]
new_command=ex_lights/landing_lights_off
dataref=sim/custom/xap/extlight/landl_sw
values=1

assign your button to the xjoymap command,,now you have what you have been dreaming for,,

That’s great news. Thanks, Ben.

2. I am happy that you get to have your cake and eat it t00. Can we have a piece of that cake also: how about (the now few) areas that were available in XP10 and still missing from XP11 and would not add much, so that you can keep the whole <60 GB.

3. I am referring to my understanding that in doing a recut, some dsf tiles were also being corrected or fixed (for tears or mis-fits, e.g.) as many had filed bug reports about them.

1. The installer should not offer to install a second copy, it gives people ideas. 😉

Hi Maurice,

1. In the future, please DO NOT do a complete re-download of the product. The new installer will be out next week and can update scenery. We put this in so that users would not feel the need to ‘just redownload everything’ – it’s not necessary and chews up bandwidth for us.

2. The recut scenery for pb13 is significantly smaller than pb1 – we fixed a DSF compresssion bug and it resulted in enough free space to be < 60 GB _and_ go to 72N. So we got to have our cake and eat it. DSFs are about 20% smaller for the same data. In pb1, a 64-bit-related bug was disabling internal DSF data compression. 3. I don't know what you mean abotu hte EArth nav data sub-folders. You should probably file a bug.

I just update my global scenery for XPpb13 and was pleasantly surprised to have the installer add several GBs of above 60 degrees tiles. The Global Scenery folder grew in size to 65.1 GBs.

It seemed to me, though, that some Earth Nav Data subfolders that need “fixed” were not. So I did a complete download of a second copy of XP11pb13 and lo and behold the Global Scenery folder in that install is only 49.5 GBs in size.

What is going on?

We don’t have date announced for this.