runway ligths (other)

[wlbragg]

please explain?

I think Hooray is referring to windows nightly builds.

As far as adding it to 3.0, I'm less sure about that as I don't know how much change has been made between now and then that might cause trouble or need to be addressed.

[MountainFlyerN22]

Thanks. Just what is Windows-nightly and what does it do?

[wlbragg]

It's the most current (hopefully stable) build of FlightGear. It contains all the new features and stuff people are working on. It's like getting the next version of FlightGear in advance, but before it's finished and optimized. So right now it's more or less FlightGear version 3.3.0.

[Hooray]

Thanks. Just what is Windows-nightly and what does it do?

Please see: http://wiki.flightgear.org/FlightGear_Build_Server

[wlbragg]

The only thing I might be concerned about with installing a nightly build or really any different or multiple versions of FlightGear is that sometimes the user/data files (semi-hidden files) can get confused between the versions and cause you trouble. If that happens all you really have to do is wipe everything FlightGear and re-install just one version and it usually works well again.
I usually have 3-7 different version or even multiples of the same versions for different things. After awhile you get used to knowing what to do to switch between them and fix stuff that gets confused.
I guess that is why I suggested editing 3.2 (if that is what you are using) rather than installing a second version, so they don't mixed up. But editing the files require you to know a little something about it also.

[Hooray]

The only thing that should involve is your $FG_HOME, which is easy enough to back up/restore - no need to delete/re-install thing from scratch.

[wlbragg]

If your referring to "C:\Users\username\AppData\Roaming\flightgear.org" then OK.
This is where I have had trouble before using a mix of versions.
Technically just deleting everything in flightgear.org and running FG again should straiten it out. But you will loose all your saves settings.
I was just forewarning MountainFlyerN22 that it can be an issue using multiple versions.
Not to mention the changes you have to make in the launcher to switch back and forth.

[wlbragg]

Technically the easiest thing to do if your running 3.2 is to backup your Shader and Effects folders and replace them with the same folder from current GIT.
That is what I did and I have all the best effects from current GIT in my 3.2 FG version. It is working fine and I don't think there is anything not accounted for or any ill effects.
It's not until you try that with the Materials that you run into trouble because there is some major differences between 3.2 Materials and GIT.
Thorsten, please correct me if I am wrong.

[Thorsten]

Technically the easiest thing to do if your running 3.2 is to backup your Shader and Effects folders and replace them with the same folder from current GIT.

Won't really work completely for the lights, as there's a correlated simgear change marking to the shader whether lights are directional or not. And will probably wreck clouds once I push the scalable transparency factor, because if that ends up being fed as zero to the shader, that's a problem.

So you might get lucky, but there's no guarantee it works in general.

[wlbragg]

there's a correlated simgear change

So there is, I didn't see that.
Thank You