Followup to VC night lighting

[ryanbatc 12,813]

So after deleting the commented-out CFG files I got the VC lighting to work at dusk, but now the light is VERY bright.And it is weird, when you turn on the lights. First you see, dark cockpit. Then for a brief second or so, the normal Pre-Acceleration VC lighting....but wait, a second later we get this nasty fricken bright crap!What the heck? The bright stuff stays enabled and I cannot tone it down.what to do next? Seems like the DX9 users got screwed here...http://forums.avsim.net/user_files/179820.jpghttp://forums.avsim.net/user_files/179821.jpghttp://forums.avsim.net/user_files/179822.jpg

[FlyingsCool 3]

I'm confused by what you said you did.If you uncommented the commented out VCLight lines from the various aircraft.cfg files, what you can do is find the associated effect and play with the lighting parameters there.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

[emwardjr 0]

I have the same problem. Also, when I first start the sim I get an automatic pause and have to "go to" the same airport again. Thanks for any advice.Ed

[ryanbatc 12,813]

I deleted the two slant marks preceding the VC light text....You mean I have to change the values too? Not sure what they mean or how to change them to a good value...For example, take this line, from the C208:light.6 = 4, -11.61, 0.00, 0.98, fx_vclightWhat does the -11.61, 0.00 and .98 mean?

[FlyingsCool 3]

The lights are basically speciallized "effects". The line in the aircraft.cfg file describes where to put the light on the model (x, y, and z from the origin of the model, I forget which order they are in), and the name of the effects file to use, in this case fx_vclight.fx, found in the FSXEffects directory. You don't need to make any changes to this line. If you want to modify the brightness of the effect, you need to modify the effects file (.fx file).The .fx files are text files that describe how the effect should work. The format is described in the SDK (found on Disk1 of the Deluxe version of FSX), but they are human (or alien) readable files and you can typically figure out the important parameters like brightness, rate of flash (if needed), etc., just by playing with them. Make sure to back them up before you edit them, but then you can make changes to your heart's content until you get what you want, or what you don't want but looks cool anyway. Work on your artistic side and post some pics!Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

[FlyingsCool 3]

Sorry, don't know anything about this. Could you describe what happens in more detail? What you said doesn't make any sense to me. Is this in multiplayer?Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

[emwardjr 0]

Yes, it is in multiplayer but I don't think this is the issue. It is really apparent flying the CRJ (default) The VC (at night) is way to bright as compared to the 2D panel which has the right intensity of night lighting. The CRJ also has so much light at night, in the VC, it makes the ADI (Attitude Direction Indicator) almost unable to see. What is interesting, is that for a brief moment the VC night panel has the correct lighting and then it goes to full blinding light. Again, the 2D panel is always OK.Regards and thanksEd Ward, JrQuad, 3 gigs, Accel, DX10, 8800 GTX

[ryanbatc 12,813]

yes, exactly how it happens for me. Have you tried the airbus? The lighting is extremely bright. I wish someone would acknowledge these issues.....jeeese

[FlyingsCool 3]

I think the night lighing issues have been acknowledged or discussed by several people.My questions pertained to the issue noted above regarding having to go to an airport twice. It is important whether it happens in multiplayer or single player or both. I also would like more information regarding exactly what happens and what the user is doing that causes the situation to occur. Does it happen every time, or just sometimes?So, given the topic here, if the OP of the original question regarding having to go to an airport twice could elaborate more on that subject, I'd like to hear that so I can check it out. I have experienced something that sounds similar to this issue in multiplayer when going to FS-MP.com using an IP address instead of going through Gamespy, and that happened in SP1, meaning it's not an SP2 thing but a multiplayer thing. I have not yet studied why it happens, as I assumed it had something to do with their checking to make sure you don't end up spawning on a runway. If it was happening in single player, then that would have been even weirder.I do not often fly at night, but, when I get a chance, I'll check out the night lighting issue as well and play with the effects files to see if that is an issue.But I assume there is a reason they commented out the VClight.fx lighting lines. I would like to hear an answer for that.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

[PhilTaylor 45]

I just blogged with a list of what aircraft are affected by this cfg change. As of this time, we have found no other change here, so removing the "commenting out" of this line in the cfg should revert this behavior.

[FlyingsCool 3]

Hi Phil,Thanks for the response. I'm wondering however, why these lines were commented out in the first place for SP2? If there were no code changes, why was the change made to the aircraft.cfg files? I can only assume there was some reasoning behind this (I don't mean to be or sound flip, I just know that you guys do things for a reason).I have not myself seen this overly bright response, so I can't comment on that. I'll try to check it out when I get home tonight. I did, however, find that this was pretty much the only change made to the aircraft.cfg files, and why my aircraft.cfg files got overwritten (grumble, grumble, - glad I had my backups). I also noticed that the camera names got "" around them. Other than that, I did not find any other changes I don't think.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180