+FastCargo Posted August 18, 2009 Posted August 18, 2009 What Wrench said. Sometimes, before you post a problem...you might want to check that you HAVE a problem first... FC
AGOSTINO Posted August 18, 2009 Author Posted August 18, 2009 Have you actually tried to get it to work? Betcha it works... FC No..... .. The lod is in one of the objects.cat. Don't worry about it, the Game Engine ™ will find it wrench kevin stein Thank you!!!! What Wrench said. Sometimes, before you post a problem...you might want to check that you HAVE a problem first... FC Sorry.......
AGOSTINO Posted August 23, 2009 Author Posted August 23, 2009 Forgive my question, but I have not yet understood, what is the "Aircraft CTD" or "CTD Planes"??
+MigBuster Posted August 23, 2009 Posted August 23, 2009 "Crash To Desktop" normally meaning the game crashes and shuts down so you are back at the Windows desktop
Guest rscsjsuso5 Posted August 23, 2009 Posted August 23, 2009 Forgive my question, but I have not yet understood, what is the "Aircraft CTD" or "CTD Planes"?? to help ctd=crash to desktop , some aircraft is too big for the airbase that the sim can't handle and to fix this problem i suggest go to your aircraft data.ini example f16data.ini and change the value to small in minbasesize=small enjoy
AGOSTINO Posted August 24, 2009 Author Posted August 24, 2009 "Crash To Desktop" normally meaning the game crashes and shuts down so you are back at the Windows desktop to help ctd=crash to desktop , some aircraft is too big for the airbase that the sim can't handle and to fix this problem i suggest go to your aircraft data.ini example f16data.ini and change the value to small in minbasesize=small enjoy I thank you, now I understand, is quite clear!!! However, I never had a problem with such!!!
AGOSTINO Posted August 26, 2009 Author Posted August 26, 2009 Some of You, know the exact values, or the fix for the "Lights Position" of the Su-39 Super Grach for SF2?? The lights are not on the frame of the plane, they're afloat!!
+Wrench Posted August 26, 2009 Posted August 26, 2009 Their positions are adjusted via data ini edits in each light callout section (ie: Positon=, as below). [LeftPositionLight] SystemType=LIGHT Position=-6.65,-0.25,-0.26 <--this line LightSrcOffset=-0.0,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.04 LightSrcRange=0.5 CanFlash=FALSE FlashTime=0.6 Having done this hundreds of times for thousands of light bulbs, I can assure you it's a mind-bending process. Move, test in game, move, test in game, move, test in game - you get the picture. Finding exactly WHERE they're supposed to be, well, that's where hours of research on the web comes into play. Or finding really good walkaround sites, books on the aircraft, detailed photos, etc. have fun!!! wrench kevin stein
AGOSTINO Posted September 1, 2009 Author Posted September 1, 2009 Their positions are adjusted via data ini edits in each light callout section (ie: Positon=, as below). Having done this hundreds of times for thousands of light bulbs, I can assure you it's a mind-bending process. Move, test in game, move, test in game, move, test in game - you get the picture. Finding exactly WHERE they're supposed to be, well, that's where hours of research on the web comes into play. Or finding really good walkaround sites, books on the aircraft, detailed photos, etc. have fun!!! wrench kevin stein I thank you, I understand the procedure, but I can't find even a night photos with lamps lit, to see where they are in reality!! Some of you have realistic pictures where can I see the lights??
+EricJ Posted September 1, 2009 Posted September 1, 2009 I would think that the Su-39 isn't at all different from the Su-25 as far as locations.
AGOSTINO Posted September 1, 2009 Author Posted September 1, 2009 (edited) This is the Fix for the lights position of the F_2A_ViperZero : // Lights --------------------------------------------------------- [LowLeftLight] SystemType=LIGHT Position=-0.70,4.502,-0.292 LightSrcOffset=-0.0,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.01 LightSrcRange=0.5 CanFlash=TRUE FlashTime=0.9 [LowRightLight] SystemType=LIGHT Position=0.70,4.502,-0.292 LightSrcOffset=0.00,0.00,0.00 Color=0.25,0.88,0.25 Brightness=0.01 LightSrcRange=0.5 CanFlash=TRUE FlashTime=0.9 [TopStrob] SystemType=LIGHT Position=0.0,-4.685,3.454 LightSrcOffset=0.00,0.00,0.00 Color=0.88,0.88,0.88 Brightness=0.02 LightSrcRange=0.2 CanFlash=TRUE FlashTime=0.5 [LeftWingLight_T] SystemType=LIGHT Position=-5.395,-0.714,0.265 LightSrcOffset=-0.0,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.02 LightSrcRange=0.7 CanFlash=TRUE FlashTime=0.9 [LeftWingLight_B] SystemType=LIGHT Position=-5.395,-0.714,0.121 LightSrcOffset=-0.0,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.02 LightSrcRange=0.7 CanFlash=TRUE FlashTime=0.9 [RightWingLight_T] SystemType=LIGHT Position=5.395,-0.714,0.265 LightSrcOffset=0.00,0.00,0.00 Color=0.25,0.88,0.25 Brightness=0.02 LightSrcRange=0.7 CanFlash=TRUE FlashTime=0.9 [RightWingLight_B] SystemType=LIGHT Position=5.395,-0.714,0.121 LightSrcOffset=0.00,0.00,0.00 Color=0.25,0.88,0.25 Brightness=0.02 LightSrcRange=0.7 CanFlash=TRUE FlashTime=0.9 Edited September 1, 2009 by AGOSTINO
AGOSTINO Posted September 2, 2009 Author Posted September 2, 2009 I would think that the Su-39 isn't at all different from the Su-25 as far as locations. I thank you, problem solved!!!
AGOSTINO Posted September 2, 2009 Author Posted September 2, 2009 This is the Fix for the lights position of the Su_39_SF2: // Lights --------------------------------------------------------- [LeftPositionLight] SystemType=LIGHT Position=-7.165,-1.295,0.63 LightSrcOffset=-0.0,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.03 LightSrcRange=0.5 CanFlash=FALSE [RightPositionLight] SystemType=LIGHT Position=7.165,-1.295,0.63 LightSrcOffset=0.00,0.00,0.00 Color=0.25,0.88,0.25 Brightness=0.03 LightSrcRange=0.5 CanFlash=FALSE [LeftPositionLight2] SystemType=LIGHT LightNodeName=LeftWing_Light CanFlash=TRUE FlashTime=0.70 [RightPositionLight2] SystemType=LIGHT LightNodeName=RightWing_Light CanFlash=TRUE FlashTime=0.70 [TopAnticollisionLight] SystemType=LIGHT Position=0.00,0.522,1.560 LightSrcOffset=0.00,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.03 LightSrcRange=0.5 CanFlash=TRUE FlashTime=0.70 [bottomAnticollisionLight] SystemType=LIGHT Position=0.00,1.463,-0.65 LightSrcOffset=0.00,0.00,0.00 Color=0.88,0.25,0.25 Brightness=0.03 LightSrcRange=0.5 CanFlash=TRUE FlashTime=0.70 [TailLight1] SystemType=LIGHT Position=-0.00,-6.240,4.070 LightSrcOffset=0.00,0.00,0.00 Color=0.88,0.88,0.88 Brightness=0.02 LightSrcRange=0.5 CanFlash=FALSE [TailLight2] SystemType=LIGHT Position=0.00,-6.240,4.070 LightSrcOffset=0.00,0.00,0.00 Color=0.88,0.88,0.88 Brightness=0.02 LightSrcRange=0.5 CanFlash=FALSE
AGOSTINO Posted September 2, 2009 Author Posted September 2, 2009 thx for this fix! You are welcome!!!!
AGOSTINO Posted September 2, 2009 Author Posted September 2, 2009 When go to the key "A", that corresponds to the autopilot, happens to me that does not work!! In the game seems to me the written: "Autopilot engaged" followed immediately by "Autopilot disengaged" Because this behavior?? The autopilot enable me and disable me simultaneously??
fougamagister Posted September 2, 2009 Posted September 2, 2009 When go to the key "A", that corresponds to the autopilot, happens to me that does not work!! In the game seems to me the written: "Autopilot engaged" followed immediately by "Autopilot disengaged" Because this behavior?? The autopilot enable me and disable me simultaneously?? Isn't it the "Q" key ? maybe your "A" is assigned to "able/disable autopilot" .. which doesn't make many sense I know !
+Fubar512 Posted September 2, 2009 Posted September 2, 2009 The A key is the TW default to toggle the autopilot, and always has been. The only reason that a model won't hold autopilot (other than a hardware issue, such as a faulty controller), would be due to an issue with the model moving or bobbing on its pitch axis. That can only be fixed by editing the model's FM.
AGOSTINO Posted September 4, 2009 Author Posted September 4, 2009 The A key is the TW default to toggle the autopilot, and always has been. The only reason that a model won't hold autopilot (other than a hardware issue, such as a faulty controller), would be due to an issue with the model moving or bobbing on its pitch axis. That can only be fixed by editing the model's FM. Thanks much, problem solved!!! The cause was the joystick!!!
jomni Posted September 4, 2009 Posted September 4, 2009 some missile pylons are also off or missing. Is that fixable?
AGOSTINO Posted September 4, 2009 Author Posted September 4, 2009 Some missile pylons are off or missing!!!
Jarhead1 Posted September 4, 2009 Posted September 4, 2009 Seriously dude, no disrespect intended, but are u gonna pick apart every airplane u download on combatace?
AGOSTINO Posted September 4, 2009 Author Posted September 4, 2009 Seriously dude, no disrespect intended, but are u gonna pick apart every airplane u download on combatace? What?? I do not understand!!!
+Wrench Posted September 4, 2009 Posted September 4, 2009 Remember how you adjusted the lights??? Well, you do the same thing with the attachment position's on the weapons station's callout in the data ini. wrench kevin stein
AGOSTINO Posted September 5, 2009 Author Posted September 5, 2009 Remember how you adjusted the lights??? Well, you do the same thing with the attachment position's on the weapons station's callout in the data ini. wrench kevin stein Thanks Wrench, I have already thought to this solution!! But the problem only occurs with two types of weapons: (1) AA - 13 and (2) R - 37 When load these two weapons, a part of the attack of the pylon not appears!! If, however load other types of weapons, the problem there is not!! Look the pictures of example:
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now