-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
FSXA Day / Night textures
- Thread starter GHD
- Start date
George,
Call it a FSX bug if you will, but what you experience is normal without compiling a Night (or LightMap) variation. I suspect Variation=Day to be default. For night, FSX renders a darkened lower resolution day photo and adds the night photo version to it. You are seeing the FSX default night lighting "bleeding" thru. These areas will flicker on/off as the photo scenery updates LODs.
The solution is to graphic process a darkened version and compile it as variation=night. I am not aware of a work around. You can use the multiple source feature to have the resultant compiled in one file containing both variants.
You will end up adding " street lights" by "dodging the exposure" to make small circles brighter than their surroundings to have an acceptable night time rendering. Others have included only the streetlight circles with all else black (0,0,0). I prefer having a darkened version of the entire photo scene for better night feature display resolution.
_w-b
Call it a FSX bug if you will, but what you experience is normal without compiling a Night (or LightMap) variation. I suspect Variation=Day to be default. For night, FSX renders a darkened lower resolution day photo and adds the night photo version to it. You are seeing the FSX default night lighting "bleeding" thru. These areas will flicker on/off as the photo scenery updates LODs.
The solution is to graphic process a darkened version and compile it as variation=night. I am not aware of a work around. You can use the multiple source feature to have the resultant compiled in one file containing both variants.
You will end up adding " street lights" by "dodging the exposure" to make small circles brighter than their surroundings to have an acceptable night time rendering. Others have included only the streetlight circles with all else black (0,0,0). I prefer having a darkened version of the entire photo scene for better night feature display resolution.
_w-b
- Messages
- 12,244
- Country
There is no doubt that it is a bug. It is not consistent in that it affects only those areas with water masks.
I have created multi-source files with a night variation using a pure black bmp and it displays correctly at night (where it is not completely black but has the photo-textures as if lit by moonlight). Dawn and dusk also display correctly.