View Full Version : V/C Light In Maule
Panther_99FS
November 17th, 2007, 13:56
No v/c light....you can obviously see where the error is..
[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit
//light.0 = 3, -1.23, -16.61, 3.08, fx_navred
//light.1 = 3, -1.23, 16.61, 3.08, fx_navgre
//light.2 = 3, -17.05, 0.00, 4.85, fx_navwhi
//light.3 = 2, -1.23, -16.61, 3.08, fx_strobe
//light.4 = 2, -1.23, 16.61, 3.08, fx_strobe
//light.5 = 4, -2.24, 0.00, 2.20, fx_vclight
Dain Arns
November 17th, 2007, 14:00
Hmmm, I don't. You look at light #5 is a type 4 = cockpit. Is it just out of place within the cockpit? I also see all your lights are rem'd out.
Dain Arns
November 17th, 2007, 14:03
Nevermind... :costumes:
Barvan40
November 17th, 2007, 14:22
Thanks Panther, that fixes the Maule lights!
Dain Arns
November 17th, 2007, 14:28
Thanks Panther, that fixes the Maule lights!
You're welcome.:rolleyes:
:costumes: :costumes: :costumes:
Panther_99FS
November 17th, 2007, 14:54
You're welcome.:rolleyes:
:costumes: :costumes: :costumes:
You should try my suggestion exactly as stated, it fixed mine (without removal of "//") :engel016:
Dain Arns
November 17th, 2007, 15:04
You should try my suggestion exactly as stated, it fixed mine (without removal of "//") :engel016:
But P, the lights are coded in the Maule now, so your edit didn't fix the problem, I don't know what did. With the "//" in place FSX ignores all information behind those marks. :kilroy:
Picture #1 is before removing the "//"
Picture #2 is after, which shows another set of lights above the wing after removing the "//"
Panther_99FS
November 17th, 2007, 15:09
But P, the lights are coded in the Maule now, so your edit didn't fix the problem, I don't know what did. With the "//" in place FSX ignores all information behind those marks. :kilroy:
It fixed for me - so I'm happy :mixedsmi:
heywooood
November 17th, 2007, 15:58
this just leads me to believe that Acceleration installed differently on some peoples' machines or there is inconsistency from one startup of the sim to the next or that the changes in lighting from FSX SP1 to Acceleration are not performing the same way on each individual machine....
anyway you slice it - there is a problem with lighting and it really needs to be addressed by Aces - or changed back to the way it was.
Why did they change it?
GypsyBaron
November 17th, 2007, 16:12
But P, the lights are coded in the Maule now, so your edit didn't fix the problem, I don't know what did. With the "//" in place FSX ignores all information behind those marks. :kilroy:
Picture #1 is before removing the "//"
Picture #2 is after, which shows another set of lights above the wing after removing the "//"
That would tend to indicate that the Nav lights are coded
into the model and the aircraft.cfg entries are superflous.
Try commenting out all BUT the VC light statement and see
what happens.
[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit
//light.0 = 3, -1.23, -16.61, 3.08, fx_navred
//light.1 = 3, -1.23, 16.61, 3.08, fx_navgre
//light.2 = 3, -17.05, 0.00, 4.85, fx_navwhi
//light.3 = 2, -1.23, -16.61, 3.08, fx_strobe
//light.4 = 2, -1.23, 16.61, 3.08, fx_strobe
light.5 = 4, -2.24, 0.00, 2.20, fx_vclight
or change it to
[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit
//light.0 = 3, -1.23, -16.61, 3.08, fx_navred
//light.1 = 3, -1.23, 16.61, 3.08, fx_navgre
//light.2 = 3, -17.05, 0.00, 4.85, fx_navwhi
//light.3 = 2, -1.23, -16.61, 3.08, fx_strobe
//light.4 = 2, -1.23, 16.61, 3.08, fx_strobe
light.0 = 4, -2.24, 0.00, 2.20, fx_vclight
Paul
Panther_99FS
November 17th, 2007, 16:28
The real perplexing thing is how folks like Piglet got it right with their aircraft but Microsoft couldn't...:banghead::isadizzy:
Killbilly
November 17th, 2007, 16:33
This is a known issue. Read Phil Taylor's blog. It's not just on the Maule, either. Several of the default planes lost their VC lighting with Acceleration. All of them have the comment mark (//) in front of the line. It's easy to fix -- just remove the comment mark. Check all your pre-Acceleration default "aircraft.cfg"s.
Panther_99FS
November 17th, 2007, 16:43
This is a known issue. Read Phil Taylor's blog.
It's not a "known issue" with Piglet's PC-7 in Acceleration....:mixedsmi::cost1:
Killbilly
November 17th, 2007, 18:38
Point taken. Maybe Tim just cares more. :d
Barvan40
November 17th, 2007, 20:23
You're welcome.:rolleyes:
:costumes: :costumes: :costumes:
Sorry Dain,
It was Panther who directed me to this post. And them it turns out after a little more testing that it was still screwed up. The Acceleration tribulation continues...:isadizzy:
Dain Arns
November 17th, 2007, 22:26
No apology needed nor wanted...
When I posted that I thought I had it quickly solved and was proud of myself. I thought it was just a simple error in the aircraft.cfg file, but real testing proved otherwise and embarrassing. :banghead:
:costumes: :costumes: :costumes:
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.