Noticed this a few times, using the OH A6M2 Zero.An AI Zero is downed and is intially counted as shot down but then does not crash, it stays airborne, constantly firing, meaning tracers firing out nonstop, if it gets on your tail its like the top ACE.Can shoot them down and a message will appear saying you shot down so and so but will not give credit, since it has already counted as shot down, basically its some bug, seen this multiple times with only the OH A6M2.Any ideas what causes this? Fix? Anyone else had this happen?
-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
Weird bug in the Zero
- Thread starter dasuto247
- Start date
Seen it multiple times now, can clearly pick it out as its only plane with a CONSTANT stream of tracers shooting into air, even if not target is in front of it. Had get on me a few times, 9/10 times it will shoot me down no matter what, it becomes super plane.
Is it possible....
...that the a\c is cloning itself? Go to the .dp file and take a look at the "effects" section. Here is what some others had to offer in the past;
Mercure sez:
To stop the cloning open with wordpad the .DP file of the considered plane and remove in the EFFECTS.X the last figure in the last effect.x line, when it appears to be one at the end of the line, between two coma.
Then do not forget to delete the .cdp file
Jaxon sez:
The key is indeed in the *.dp file.
Your plane is probably not a stock one.
But the *.dp file is based on one of the stockers.
In there it looks like this:
[EFFECTS.25]
; System = Rudder
effect.0=95,LIBRARY,fx_smkpuff_s,
effect.1=100,BREAK,12,
I once had a problem similar to yours where I would shoot a plane and it would fall, but another would then be in its' place. Did what was suggested and it plane solved it.
(Couldn't resist the pun!)
...that the a\c is cloning itself? Go to the .dp file and take a look at the "effects" section. Here is what some others had to offer in the past;
Mercure sez:
To stop the cloning open with wordpad the .DP file of the considered plane and remove in the EFFECTS.X the last figure in the last effect.x line, when it appears to be one at the end of the line, between two coma.
Then do not forget to delete the .cdp file
Jaxon sez:
The key is indeed in the *.dp file.
Your plane is probably not a stock one.
But the *.dp file is based on one of the stockers.
In there it looks like this:
[EFFECTS.25]
; System = Rudder
effect.0=95,LIBRARY,fx_smkpuff_s,
effect.1=100,BREAK,12,
I once had a problem similar to yours where I would shoot a plane and it would fall, but another would then be in its' place. Did what was suggested and it plane solved it.
(Couldn't resist the pun!)...that the a\c is cloning itself? Go to the .dp file and take a look at the "effects" section. Here is what some others had to offer in the past;
Mercure sez:
To stop the cloning open with wordpad the .DP file of the considered plane and remove in the EFFECTS.X the last figure in the last effect.x line, when it appears to be one at the end of the line, between two coma.
Then do not forget to delete the .cdp file
Jaxon sez:
The key is indeed in the *.dp file.
Your plane is probably not a stock one.
But the *.dp file is based on one of the stockers.
In there it looks like this:
[EFFECTS.25]
; System = Rudder
effect.0=95,LIBRARY,fx_smkpuff_s,
effect.1=100,BREAK,12,
I once had a problem similar to yours where I would shoot a plane and it would fall, but another would then be in its' place. Did what was suggested and it plane solved it.
Thanks, I will try it out.Plane is the OH A6M2 by B24guy so yes based on stock DP.
...that the a\c is cloning itself? Go to the .dp file and take a look at the "effects" section. Here is what some others had to offer in the past;
Mercure sez:
To stop the cloning open with wordpad the .DP file of the considered plane and remove in the EFFECTS.X the last figure in the last effect.x line, when it appears to be one at the end of the line, between two coma.
Then do not forget to delete the .cdp file
Jaxon sez:
The key is indeed in the *.dp file.
Your plane is probably not a stock one.
But the *.dp file is based on one of the stockers.
In there it looks like this:
[EFFECTS.25]
; System = Rudder
effect.0=95,LIBRARY,fx_smkpuff_s,
effect.1=100,BREAK,12,
I once had a problem similar to yours where I would shoot a plane and it would fall, but another would then be in its' place. Did what was suggested and it plane solved it.
Using the OH A6M2 by B24 guy.I am still not 100% what to do.I attached the DP below
Fibber
From my testing the Rudder and Elevators can have break with numbers. The numbers below will cause them to change to the damage texture with aircraft that use damage texture logic. I think at one time CFS2 was going to make more use of damage texture logic more but is seem to have been scraped. The Rudder and Elevators seem to work just fine with the right numbers in the DP. Some of the stock aircraft DPs seem to still use the starboard elevator number but it is applied to the rudder as shown in the code you posted.
Port elevator
in .DP file
effect.#=100,BREAK,11,
In DPED
Pram1 box put 11
Starboard elevator
in .DP file
effect.#=100,BREAK,12,
In DPED
Pram1 box put 12
Rudder
in .DP file
effect.#=100,BREAK,13,
In DPED
Pram1 box put 13
From my testing the Rudder and Elevators can have break with numbers. The numbers below will cause them to change to the damage texture with aircraft that use damage texture logic. I think at one time CFS2 was going to make more use of damage texture logic more but is seem to have been scraped. The Rudder and Elevators seem to work just fine with the right numbers in the DP. Some of the stock aircraft DPs seem to still use the starboard elevator number but it is applied to the rudder as shown in the code you posted.
Port elevator
in .DP file
effect.#=100,BREAK,11,
In DPED
Pram1 box put 11
Starboard elevator
in .DP file
effect.#=100,BREAK,12,
In DPED
Pram1 box put 12
Rudder
in .DP file
effect.#=100,BREAK,13,
In DPED
Pram1 box put 13
Allen........
...I just posted what the instructions I was given when I had the same problem awhile back with some missions. It seemed I was flaming the same plane ad-infinum and it was not limited to just the Zero! I removed the numbers in the affected planes and the problem(s) ceased. That is why I did include, as references, the instructions of the others. Now as to what "effects" controls what part I don't know.
...I just posted what the instructions I was given when I had the same problem awhile back with some missions. It seemed I was flaming the same plane ad-infinum and it was not limited to just the Zero! I removed the numbers in the affected planes and the problem(s) ceased. That is why I did include, as references, the instructions of the others. Now as to what "effects" controls what part I don't know.
It could be that the Rudder and Elevators damage code was messed up when it was SCASM edited by TheB24Guy.
EDIT:
Not related to the Rudder and Elevators break numbers. Usung them works fine with the model.
EDIT2:
Another things is that it could be away to ID what part is causing the clone plane to fall by using [CHEATS] with in the main folder's CFS2.cfg.
Drop the below into your CFS2.cfg and change damagemsgs=0 to damagemsgs=1 This will show you what part of the plane you have shot.
[CHEATS]
bomb_trainer=0
free_warp=0
ALLOW_SLEW=0
damagemsgs=0
oneshot_kill=0
EDIT:
Not related to the Rudder and Elevators break numbers. Usung them works fine with the model.
EDIT2:
Another things is that it could be away to ID what part is causing the clone plane to fall by using [CHEATS] with in the main folder's CFS2.cfg.
Drop the below into your CFS2.cfg and change damagemsgs=0 to damagemsgs=1 This will show you what part of the plane you have shot.
[CHEATS]
bomb_trainer=0
free_warp=0
ALLOW_SLEW=0
damagemsgs=0
oneshot_kill=0
Last edited: