My server has a new install and my Left view client one from April 2021. Both Premium de Luxe. Both the same Scenery settings.

As I use WidevieW to sync the views this morning I was trying to “connect” the views a little more precise. At EHAM (Amsterdam).

Then I saw that the Left view client had red/white lines on the tarmac that did not continue on the server :

https://www.dropbox.com/s/nivt87enb11fj8l/Foto 30-07-2021 10 19 27.jpg?dl=0

I am talking about this that does not show on my server :

https://www.dropbox.com/s/ltyp9a01s51412l/Foto 30-07-2021 10 21 20.jpg?dl=0

So I checked the EHAM folder size :

server 33,2 mb / client 71,8 mb

 

I checked other airports :

EGGL :  server 83,7 mb / client 52,8 mb 

EDDF :  server 259 mb / client 412 mb

 JFK :   both 206 mb 

Capetown : server 37,4 mb / client 52,8 mb 

 

All airports that match the server on my client are dated 28 July 2021.

All airports that have a different size than the server show 16 July 2021.

Just because I have 2 view pc’s I saw this.

What is going on here ? Some are now less detailed in order to get better FPS ?

Or is there something else going on ?

- - - 

My issue was caused by Zinertek airport textures that were not installed yet….

 

 

 

 

 

Edited July 30, 20214 yr by GSalden

They are working to take them away from you. Guns and bibles next.

The reduction in size for sceneries rebuilt using the latest SDK can be explained by this sentence on the SDK:

https://docs.flightsimulator.com/html/index.htm#t=Asset_Creation%2FTextures.htm
 

IMPORTANT! Previously high quality was always set for AO/Roughness/Metal (COMP) textures by default, but this was changed in a recent update. Therefor, before publishing any new packages - or updating existing packages - you may need to add the high quality flag if you see compression issues with those textures. Keep in mind that you can check the visuals of any texture map in the simulation using the PBR Channel render debug window.

and:
 

NOTE: These flags should be used carefully, as they can have a serious performance impact when abuse

This means the AO/Roughness/Metal textures now take HALF the size compared to previous versions, because they now use BY DEFAULT ( unless the developers specifies otherwise, by settings some override .FLAGS files ) use DXT1 compression instead of DXT5

2 hours ago, virtuali said:

The reduction in size for sceneries rebuilt using the latest SDK can be explained by this sentence on the SDK:

https://docs.flightsimulator.com/html/index.htm#t=Asset_Creation%2FTextures.htm
 

IMPORTANT! Previously high quality was always set for AO/Roughness/Metal (COMP) textures by default, but this was changed in a recent update. Therefor, before publishing any new packages - or updating existing packages - you may need to add the high quality flag if you see compression issues with those textures. Keep in mind that you can check the visuals of any texture map in the simulation using the PBR Channel render debug window.

and:
 

NOTE: These flags should be used carefully, as they can have a serious performance impact when abuse

This means the AO/Roughness/Metal textures now take HALF the size compared to previous versions, because they now use BY DEFAULT ( unless the developers specifies otherwise, by settings some override .FLAGS files ) use DXT1 compression instead of DXT5

Umberto,

That I understand. But why do I see different sizes in multiple default sceneries on 2 pc’s having both the same version installed ?

thanks,

Gerard

20 minutes ago, GSalden said:

But why do I see different sizes in multiple default sceneries on 2 pc’s having both the same version installed ?

They cannot possibly be the same version. One must have been compiled with an earlier version of the sim ( many users assume the SDK version matters, but it doesn't, what really matters is the version of the sim which was installed when the scenery was built )

38 minutes ago, virtuali said:

They cannot possibly be the same version. One must have been compiled with an earlier version of the sim ( many users assume the SDK version matters, but it doesn't, what really matters is the version of the sim which was installed when the scenery was built )

The show the same version number.

Only one has been installed in April and the other yesterday.

And these are P de L default airports.

Both pc’s have all updates…

11 minutes ago, GSalden said:

The show the same version number.

Nothing ensure the version number would change by simply rebuilding the scenery with a new version. It must be changed manually by the developer.