• 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.

Color correction

jonmkj

jonmkj

Messages
795
Country
us-northcarolina
So I have a high resolution aerial of an airport. When I put it into FSX, it's a completely different shade of color as compared to the surrounding terrain. What is the best method of color matching it while retaining the image clarity and crispness?
 
Awesome! Just what I was looking for. Thank you very much for the speedy reply!
 
Hi,

The PaintDotnet plugin (color match) does not seem to work well. At least not on my PC. Had lots of time "run out of memory" messages and when it finally worked the original BMP had become blurry and the colors were not right. Maybe others have different results?
 
Hi robystar

Paint.net is written in the 32-bit .Net environment. It will suffer the same memory problems that SBuilderX suffers with very large images. Breaking source images into smaller images would help.

Any blurring of the 'colorized' final image could be due to the Color Match plugin's interpolation, or could be due to a number of factors... your hardware, resample, FSX display engine...

As the other thread mentioned, Metrix works for Photoshop or PaintShopPro as a plugin. But I think the process uses the same algorithm.

EDITED+++++++++++++++

Apparently Paint.Net does have 64 bit capability, and is detected upon the program installation. So if you have a 64-bit operating system, you'll get the greater memory benefits.

Dick
 
Last edited:
Hi Dick,

(Had some trouble finding back this thread)
Gimp 2.6 solved my problem with the GEGL plugin and then choose color temperature. With trial and error and a good pair of eyes, my photo scenery now matches well the FSX default surrounding scenery.
Just to let you know and for what it is worth.

Roby
 
I use the match color function in the 64 bit Photoshop CS5. It's amazingly quick. I then resend the tif through Global Mapper before resample.

Jim
 
I would stronly suggest, BEFORE you start color correcting Photo Scenery, you make sure your Monitor is fully calibrated, both for Color Temperature, as well as for Correct Gamma, Black Level and White Level.

There is little point in Color Correcting your Scenery to look good on YOUR Monitor, if Your Monitor is out of Calibration, making your scenery look different on other people, more calibrated monitors.

Geoff
 
How many users even know that their monitor is calibrated properly, or that there's any need to do so?

Fortunately, most monitors are pretty much calibrated when new, and unlike the ancient CRTs, don't change much -if any- as they age. ;)
 
You know ... it actually doesn't matter what your monitor colour settings are ...

until you start making things that OTHER people will use.

Then you can get some rude shocks when you see screenshots from other users computers of your work! :eek:
 
One of the most critical setting when working in FSX, is your Black Level.
It is very critical, when you are looking at any NIGHT scenes.
So is gamma.

Having the optimum Black level & Gamma, can make an ENORMOUS difference to your experience when flying at night in FSX.

Also, for a given Monitor setting, there is a very significant Improvement in lighting at Night in P3D, vs FSX. Interesting improvements in P3D. Shaders ??

Geoff
 
That is one of the reasons why I finally dumped all of my aging CRT monitors several years ago (I actually donated them to the local library), and replaced all of 'em with quality LCD displays.

Everyone of which has been calibrated for proper color, gamma and black level. It keeps me from being surprised when testing stuff on different rigs here at my home office!
 
n4gix said:
That is one of the reasons why I finally dumped all of my aging CRT monitors several years ago (I actually donated them to the local library), and replaced all of 'em with quality LCD displays.

Everyone of which has been calibrated for proper color, gamma and black level. It keeps me from being surprised when testing stuff on different rigs here at my home office!
Click to expand...

So Bill, with Correctly Calibrated monitors, do you have any comments or observation about the difference in display, between FSX & P3D.(especailly in night scenes).

For me, running the same scenery in P3D, is like I have taken CLARITIN, and the scene has taken on a new clarity.

Also, in P3D, at night, the sky is full of stars !!!

Amazing

Geoff
 
Geoff, all things being equal, I too can see a marked difference in the clarity and crispness of Prepar3D myself.

As an aside though, I have noticed that Prepar3D is much less tollerant of minor XML syntax errors. Several XML scripts that work flawlessly in FSX won't load without a "bitch session" poping up in Prepar3D...

...which on consideration is actually a "Good Thing," since it allows me to identify and correct the minor errors! :rotfl:
 
n4gix said:
Geoff, all things being equal, I too can see a marked difference in the clarity and crispness of Prepar3D myself.

As an aside though, I have noticed that Prepar3D is much less tollerant of minor XML syntax errors. Several XML scripts that work flawlessly in FSX won't load without a "bitch session" poping up in Prepar3D...

...which on consideration is actually a "Good Thing," since it allows me to identify and correct the minor errors! :rotfl:
Click to expand...


I've also noticed the that P3D is less tollerant of minor XML syntax errors, but seems to run a little faster. ? -- also a "Good Thing".

The $64,000 is, will P3D run the RADAR gauges, without locking up the sim. like it did in FSX.

Geoff
 
You must log in or register to reply here.
Back
Top