FF5.5 Tiger Spirit campaign test - Winnable.

[ccc]

Since my tests with PMC TCL-campaigns can not achieve a win/lose ending, i started a default FF5.5 cam for comparsion.

i picked Tiger spirit, ran at 16x in 2d, joined some flights for AG missions.
http://i112.photobucket.com/albums/n192 ... /ghhtr.jpg

though it's winnable, my impressions listed here..
- the pic shows i've cleared ALL red GUs in Wonson, and MOST red GUs in P'yongyang, few blue GUs are close to take them. Blue dominates the air. it's just a matter of time to win - so i speed it up by ordering a nearby GU to capture Wonson. Since TRI setting for Victory condition is capturing Wonson OR P'yongyang, the war ended once that GU got Wonson on Day 5.. earlier than AI planned.
- the cam ran thru offensive- defenisve-consolidatoin-major offensive cycle in first three days. At first i thought Blue will lose and unable to move north, as Red made aggressive offensive from air and land. the situation stablized on day 3, then Blue turned on major offensive.
- all event movies played, adequately.
- experienced two RED air power surges, one is Russian joining the war, and the other is China joining the war. the air situation is somewhat overwhelming.. but stablized later.
- Though blue on major offensive, i noted the advancing GUs are fewer than old day falcon versions!! AFAIR, in RV there're more GUs moving on major offensive, like "flow of steel". in FF5.5 it looks the flow of GUs is thinner, weaker, and scattering. Old day falcons there're THREE main advancing routes-- left, middel, and east routes. in this test all three routes has much fewer GUs moving.. thanx to air support, blue GUs still can move to their goals - without hot contact with Red GUs.
- dunno whether it's DB or AI brain issue, the GU vs GU fighting is fewer than old day versions. also GUs are less brave to engage enemies - they tend to count on CAS and stay away from red GUs. in my old day test, i noted GUs aggressively engaged Red units and took obj.. in this version i found the GU aggressiveness is lowered.
- the pic also shows Blue has MANY towed artillery and SPG units along DMZ.. they won't join the offensive, just stayed there till the war ended.
- even so.. thanx God those GUs move, and campaign can reach an end.. tho in a less exotic way.
- as for simming in 3d world, i experienced MANY CTDs. Some happened while approaching GUs for bombing - it seems a de-aggregating bug, the other, or most CTDs happened when loading in second pie, reported as "can not Get Radar type " error... it made me unable to highjack flights( with tweaked AG ordance).. and such CTDs mostly happened in later days of campaign.

[molnibalage]

Sorry for the asking but the big question to me that is there any campaign that is winnable to red side?

[derStef]

Sorry for the asking but the big question to me that is there any campaign that is winnable to red side?

yeah in Taiwan, my friend.

[demer928]

Sorry for the asking but the big question to me that is there any campaign that is winnable to red side?

yeah in Taiwan, my friend.

AND soon to be in Iran....

demer

[ccc]

Sorry for the asking but the big question to me that is there any campaign that is winnable to red side?

in old falcon versions like RV, or modded ones by DoctorX's, yes Red side can win.

for latest FF5.5 cams, i don't know.

[Hustler]

Of course..the code does not weight the result based on Team color. If you build Campaigns that work and you fly on the Red side, you can win. When we tested the current Campaigns in FF, we had several instances where Red won the War, because there was no Blue human pilot. Once again, if everything is equal, the advantage goes to the side with the human player, just as Microprose intended.

Sorry for the asking but the big question to me that is there any campaign that is winnable to red side?

[ccc]

In last test i ordered one unit to capture Wonson, thus ended the war on day 5.

To check if AI can take wonson by itself, i loaded an earlier cam, kept runing at 16x without intervension.. yes, ground war AI can win by capturing Wonson. the new test ended on Day 4 1600.
i also found ATO unable to offer CAS at hot spots.. the only CAS ac, A10s, were sent to p'yongyang area, not the target of major offensive, Wonson.
-------------------------------

I don't know why FF5.5 TRI use "capture Wonson OR P'yongyang" for Blue vicotry. In older falcons, TRI uses "AND" instead, probably means old campaigns have sufficient ground power to take BOTH obj.

To check if FF5.5 cam can capture BOTH obj, i edited the TRI and let it running at 16x, till Day 6.

- i noted Blue GUs at West and middle combat routes remained immobile, due to exhausted or other reasons.
- three GUs moved to P'yongyang area, one captured Cheonon, the other two stayed near P'yongyang area, refused to move further. All three units came from East route GUs/Wonson area.
- SPG and towed gun GUs along north DMZ remained totally immoblie. too bad.
- two SpecOp units from East coast GUs are on their way toward P'yongyang.. sigh , it seems they could be the last hope to capture P'yongyang..because they are the only two moving during major offensive.
- i can not jump in any flights now. sometimes CTDs happened at 2nd pie, or the end of loading screen. all crashlog txt are the same, said:
unitclass::GetRadarType, some ALR56... bug?

Code: Select all

FFViper.exe caused a EXCEPTION_ACCESS_VIOLATION in module FFViper.exe at 0023:00652520, UnitClass::GetRadarType()+112 byte(s)
Exception handler called in SimLoop Thread.
Read from location 0a3d99ee caused an access violation.
Code: 0f bf 40 38 eb 02 33 c0 8b e5 5d c3 cc cc cc cc 
Stack dump:
Stack: 0023:00652520 (0x00000000 0x1911E000 0x27E6E208 0x006AB6FF) FFViper.exe, UnitClass::GetRadarType()+112 byte(s)
Stack: 0023:008F840C (0x1911E508 0x27E6E208 0x00000000 0x09F7F728) FFViper.exe, ALR56Class::GetLethality()+76 byte(s)
Stack: 0023:00714769 (0x1911E508 0x27CF09E0 0x3E679AAC 0x00000000) FFViper.exe, PlayerRwrClass::IsFiltered()+41 byte(s)
Stack: 0023:00712DCE (0x16CF0418 0x27CEFBA8 0x00000000 0x27E6E208) FFViper.exe, PlayerRwrClass::Exec()+910 byte(s)
Stack: 0023:0076DF1B (0x00000000 0x26EA0000 0x00000000 0x0000077F) FFViper.exe, AircraftClass::RunSensors()+395 byte(s)
Stack: 0023:0076BCF9 (0x27CE1F20 0x27CEFBA8 0x20528954 0x09F7FE50) FFViper.exe, AircraftClass::Exec()+9481 byte(s)
Stack: 0023:0072C360 (0x20528954 0x09F7FE2C 0x27CE1F20 0x09F7FEB8) FFViper.exe, SimVuDriver::ExecModel()+32 byte(s)
Stack: 0023:006AA942 (0x20528954 0x00000000 0x00000000 0x27CE1F20) FFViper.exe, VuMaster::Exec()+50 byte(s)
Stack: 0023:0078A094 (0x00000001 0x024D4988 0x00000000 0x00000000) FFViper.exe, SimulationDriver::Cycle()+836 byte(s)
Stack: 0023:00719DC1 (0x00000000 0x00000000 0x00000000 0x00000000) FFViper.exe, SimulationLoopControl::Loop()+1393 byte(s)
Stack: 0023:00719554 (0x00000000 0x09F7FFD4 0x77709D42 0x00000000) FFViper.exe, SimLoopWrapper()+68 byte(s)
Stack: 0023:76123677 (0x00000000 0x7EA4D766 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+18 byte(s)
Stack: 0023:77709D42 (0x00719510 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+99 byte(s)
Stack: 0023:77709D15 (0x00000000 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+54 byte(s)
EAX=0A3D99B6  EBX=00000000  ECX=FFFFFFAF  EDX=190D3008  ESI=20528954
EDI=00000000  EBP=00000000  ESP=09F7FFF4  EIP=00000000  FLG=00010202
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B
Error occurred at 8/30/2010 22:32:14.
C:\FreeFalcon5\FFViper.exe, run by CCC.
2 processor(s), type 586.
4063 MBytes physical memory.
OS: 6.1 build 7600 platform 2 
Version: Falcon 4.0 - Version 1.13.1.20422
FFViper : 2, 3, 3, 5
Card: DXContext::Init - DriverInfo - "atiumdag.dll" - "ATI Mobility Radeon HD 4570  ", Vendor: 4098, Device: 38227, SubSys: -1875701683, Rev: 0, Product: 0, Version: 0, SubVersion: 0, Build: 0

Game is Campaign type Local
DX Model ID : ffffffff
Texture ID  : ffffffff

[ccc]

another random CTD in 2d map..

Code: Select all

FFViper.exe caused a EXCEPTION_ACCESS_VIOLATION in module FFViper.exe at 0023:005E42D2, BattalionClass::CanShootWeapon()+114 byte(s)
Exception handler called in Campaign Thread.
Read from location 0a013620 caused an access violation.
Code: 0f bf 48 38 69 c9 b4 00 00 00 03 0d bc 4b b3 00 
Stack dump:
Stack: 0023:005E42D2 (0x000000C9 0x0000DAC0 0x00000000 0x120A7DF8) FFViper.exe, BattalionClass::CanShootWeapon()+114 byte(s)
Stack: 0023:006539DC (0x0C28745D 0x00000005 0x0A1BFE7C 0x0A1BFE9C) FFViper.exe, UnitClass::CollectWeapons()+412 byte(s)
Stack: 0023:0043B07C (0x120A7DF8 0x120823D8 0x120A7DF8 0x00000000) FFViper.exe, DoCombat()+540 byte(s)
Stack: 0023:005E364F (0x00000000 0x006A1013 0x0A1BFF1C 0x00000000) FFViper.exe, BattalionClass::DoCombat()+351 byte(s)
Stack: 0023:0043AB9E (0x120A7DF8 0x000000F0 0x0A1BFF28 0x120A7C80) FFViper.exe, UpdateUnit()+478 byte(s)
Stack: 0023:0043536F (0x000000F0 0x00000000 0x0C27B908 0x0000000A) FFViper.exe, UpdateRealUnits()+223 byte(s)
Stack: 0023:00434AB0 (0x00000000 0x00000000 0x00000000 0x00000000) FFViper.exe, HandleCampaignThread()+688 byte(s)
Stack: 0023:00434B99 (0x00000000 0x0A1BFFD4 0x77709D42 0x00000000) FFViper.exe, CampaignThread()+57 byte(s)
Stack: 0023:76123677 (0x00000000 0x7D17CB11 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+18 byte(s)
Stack: 0023:77709D42 (0x00434B60 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+99 byte(s)
Stack: 0023:77709D15 (0x00434B60 0x00000000 0x00000000 0x0E460000) ntdll.dll, RtlInitializeExceptionChain()+54 byte(s)
EAX=0A0135E8  EBX=00000000  ECX=FFFFFFAF  EDX=0C230048  ESI=0C9B54B0
EDI=00000FA0  EBP=00000000  ESP=0A1BFFF4  EIP=00000000  FLG=00010286
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B
Error occurred at 8/30/2010 23:38:30.
C:\FreeFalcon5\FFViper.exe, run by CCC.
2 processor(s), type 586.
4063 MBytes physical memory.
OS: 6.1 build 7600 platform 2 
Version: Falcon 4.0 - Version 1.13.1.20422
FFViper : 2, 3, 3, 5
Card: DXContext::Init - DriverInfo - "atiumdag.dll" - "ATI Mobility Radeon HD 4570  ", Vendor: 4098, Device: 38227, SubSys: -1875701683, Rev: 0, Product: 0, Version: 0, SubVersion: 0, Build: 0

Game is Campaign type Local
DX Model ID : 0
Texture ID  : 0

run the cam at 16x to Day 8.
- only one armour unit moving.. toward north of Wonson. no GUs want to capture p'yongyang.
- totally unable to join any ac in 3d. CTD all the same as GetRadarType crashlog.
- all Red ac icons in 2d map turn into unknonw/triangle.. even blue ac engaged them at close distance, all red icon remain triangle = red ac type unknown. the event report just said " DPRK ac shot down at .. ", unable to tell the true ac type.
- 99.9% of blue GUs are static.

[ccc]

in this F5.5 cam,

i found GUs are visible as Battalion icon only in 2d map. GUs has no "brigade" or "division" setting, so.. no GUs show as brigade or divisoin in 2d map.
it means the ground war AI command directly transmit to basic battalion unit? God knows.. it could also explains the lack of grouped GU movement.
IIRC, Brigade could be the unit receiving ground war AI command, not the battlion.

anyway, the GU movement in this cam is lack of coordination.. and ground war just too plain.

[Hustler]

If you are posting crash logs looking for support then please install the latest upgrade. There is a crash log thread on the FF Forums, follow the proper procedures by providing the information essential for support and post your crash logs there.

another random CTD in 2d map..

Code: Select all

FFViper.exe caused a EXCEPTION_ACCESS_VIOLATION in module FFViper.exe at 0023:005E42D2, BattalionClass::CanShootWeapon()+114 byte(s)
Exception handler called in Campaign Thread.
Read from location 0a013620 caused an access violation.
Code: 0f bf 48 38 69 c9 b4 00 00 00 03 0d bc 4b b3 00 
Stack dump:
Stack: 0023:005E42D2 (0x000000C9 0x0000DAC0 0x00000000 0x120A7DF8) FFViper.exe, BattalionClass::CanShootWeapon()+114 byte(s)
Stack: 0023:006539DC (0x0C28745D 0x00000005 0x0A1BFE7C 0x0A1BFE9C) FFViper.exe, UnitClass::CollectWeapons()+412 byte(s)
Stack: 0023:0043B07C (0x120A7DF8 0x120823D8 0x120A7DF8 0x00000000) FFViper.exe, DoCombat()+540 byte(s)
Stack: 0023:005E364F (0x00000000 0x006A1013 0x0A1BFF1C 0x00000000) FFViper.exe, BattalionClass::DoCombat()+351 byte(s)
Stack: 0023:0043AB9E (0x120A7DF8 0x000000F0 0x0A1BFF28 0x120A7C80) FFViper.exe, UpdateUnit()+478 byte(s)
Stack: 0023:0043536F (0x000000F0 0x00000000 0x0C27B908 0x0000000A) FFViper.exe, UpdateRealUnits()+223 byte(s)
Stack: 0023:00434AB0 (0x00000000 0x00000000 0x00000000 0x00000000) FFViper.exe, HandleCampaignThread()+688 byte(s)
Stack: 0023:00434B99 (0x00000000 0x0A1BFFD4 0x77709D42 0x00000000) FFViper.exe, CampaignThread()+57 byte(s)
Stack: 0023:76123677 (0x00000000 0x7D17CB11 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+18 byte(s)
Stack: 0023:77709D42 (0x00434B60 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+99 byte(s)
Stack: 0023:77709D15 (0x00434B60 0x00000000 0x00000000 0x0E460000) ntdll.dll, RtlInitializeExceptionChain()+54 byte(s)
EAX=0A0135E8  EBX=00000000  ECX=FFFFFFAF  EDX=0C230048  ESI=0C9B54B0
EDI=00000FA0  EBP=00000000  ESP=0A1BFFF4  EIP=00000000  FLG=00010286
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B
Error occurred at 8/30/2010 23:38:30.
C:\FreeFalcon5\FFViper.exe, run by CCC.
2 processor(s), type 586.
4063 MBytes physical memory.
OS: 6.1 build 7600 platform 2 
Version: Falcon 4.0 - Version 1.13.1.20422
FFViper : 2, 3, 3, 5
Card: DXContext::Init - DriverInfo - "atiumdag.dll" - "ATI Mobility Radeon HD 4570  ", Vendor: 4098, Device: 38227, SubSys: -1875701683, Rev: 0, Product: 0, Version: 0, SubVersion: 0, Build: 0

Game is Campaign type Local
DX Model ID : 0
Texture ID  : 0

run the cam at 16x to Day 8.
- only one armour unit moving.. toward north of Wonson. no GUs want to capture p'yongyang.
- totally unable to join any ac in 3d. CTD all the same as GetRadarType crashlog.
- all Red ac icons in 2d map turn into unknonw/triangle.. even blue ac engaged them at close distance, all red icon remain triangle = red ac type unknown. the event report just said " DPRK ac shot down at .. ", unable to tell the true ac type.
- 99.9% of blue GUs are static.

[Hustler]

This Campaign contains the same number of GU's as before, none were removed as you have guessed. You are correct, the .tri file was changed to read capture Wonson or Pyongyang. We decided the capture of both was not required to meet our goal in the design of a Campaign lasting just a few days.

Your continued testing of Campaigns at 16X is flawed. It is well documented that 16X is the MAX you can push the 2D calculations and not crash out. 8X returns better results, 4X better yet. You also seem to continue to rely strictly on high speed, no human player interaction, or testing. This is totally wrong, and is counter to the published Manual, which clearly states that the human players performance effects the outcome of the battle. There are many areas in the code that define an action, based upon the players result. If running Campaigns at 16X on my PC returned accurate results, why would every development Group now and in the past use BETA Testers?

I am also puzzled by your fascination with GU movements. Isn't this a flight sim? It is our opinion that as long as there is movement of forces on the ground, that presents the perception of action and provides a dynamic list of targets for a human pilot to attack, you have a working Campaign. If those GU's can actually advance and take an Objective, given assistance from Air forces, you have a really good Campaign. If I were to make a suggestion to you and others here it would be to quit spending all of this time and effort trying to figure out the irrelevant and obviously elusive to you, ground unit movement questions. This is a flight simulator and the Pilots on the FreeFalcon Forums are more interested in the particulars of flying the F-117, the A-10, or the fact that I have porked the radar in the Jaguar. I have not read 1 post commenting about a lack of GU movement or what my .tri files look like.

In last test i ordered one unit to capture Wonson, thus ended the war on day 5.

To check if AI can take wonson by itself, i loaded an earlier cam, kept runing at 16x without intervension.. yes, ground war AI can win by capturing Wonson. the new test ended on Day 4 1600.
i also found ATO unable to offer CAS at hot spots.. the only CAS ac, A10s, were sent to p'yongyang area, not the target of major offensive, Wonson.
-------------------------------

I don't know why FF5.5 TRI use "capture Wonson OR P'yongyang" for Blue vicotry. In older falcons, TRI uses "AND" instead, probably means old campaigns have sufficient ground power to take BOTH obj.

To check if FF5.5 cam can capture BOTH obj, i edited the TRI and let it running at 16x, till Day 6.

- i noted Blue GUs at West and middle combat routes remained immobile, due to exhausted or other reasons.
- three GUs moved to P'yongyang area, one captured Cheonon, the other two stayed near P'yongyang area, refused to move further. All three units came from East route GUs/Wonson area.
- SPG and towed gun GUs along north DMZ remained totally immoblie. too bad.
- two SpecOp units from East coast GUs are on their way toward P'yongyang.. sigh , it seems they could be the last hope to capture P'yongyang..because they are the only two moving during major offensive.
- i can not jump in any flights now. sometimes CTDs happened at 2nd pie, or the end of loading screen. all crashlog txt are the same, said:
unitclass::GetRadarType, some ALR56... bug?

Code: Select all

FFViper.exe caused a EXCEPTION_ACCESS_VIOLATION in module FFViper.exe at 0023:00652520, UnitClass::GetRadarType()+112 byte(s)
Exception handler called in SimLoop Thread.
Read from location 0a3d99ee caused an access violation.
Code: 0f bf 40 38 eb 02 33 c0 8b e5 5d c3 cc cc cc cc 
Stack dump:
Stack: 0023:00652520 (0x00000000 0x1911E000 0x27E6E208 0x006AB6FF) FFViper.exe, UnitClass::GetRadarType()+112 byte(s)
Stack: 0023:008F840C (0x1911E508 0x27E6E208 0x00000000 0x09F7F728) FFViper.exe, ALR56Class::GetLethality()+76 byte(s)
Stack: 0023:00714769 (0x1911E508 0x27CF09E0 0x3E679AAC 0x00000000) FFViper.exe, PlayerRwrClass::IsFiltered()+41 byte(s)
Stack: 0023:00712DCE (0x16CF0418 0x27CEFBA8 0x00000000 0x27E6E208) FFViper.exe, PlayerRwrClass::Exec()+910 byte(s)
Stack: 0023:0076DF1B (0x00000000 0x26EA0000 0x00000000 0x0000077F) FFViper.exe, AircraftClass::RunSensors()+395 byte(s)
Stack: 0023:0076BCF9 (0x27CE1F20 0x27CEFBA8 0x20528954 0x09F7FE50) FFViper.exe, AircraftClass::Exec()+9481 byte(s)
Stack: 0023:0072C360 (0x20528954 0x09F7FE2C 0x27CE1F20 0x09F7FEB8) FFViper.exe, SimVuDriver::ExecModel()+32 byte(s)
Stack: 0023:006AA942 (0x20528954 0x00000000 0x00000000 0x27CE1F20) FFViper.exe, VuMaster::Exec()+50 byte(s)
Stack: 0023:0078A094 (0x00000001 0x024D4988 0x00000000 0x00000000) FFViper.exe, SimulationDriver::Cycle()+836 byte(s)
Stack: 0023:00719DC1 (0x00000000 0x00000000 0x00000000 0x00000000) FFViper.exe, SimulationLoopControl::Loop()+1393 byte(s)
Stack: 0023:00719554 (0x00000000 0x09F7FFD4 0x77709D42 0x00000000) FFViper.exe, SimLoopWrapper()+68 byte(s)
Stack: 0023:76123677 (0x00000000 0x7EA4D766 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+18 byte(s)
Stack: 0023:77709D42 (0x00719510 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+99 byte(s)
Stack: 0023:77709D15 (0x00000000 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+54 byte(s)
EAX=0A3D99B6  EBX=00000000  ECX=FFFFFFAF  EDX=190D3008  ESI=20528954
EDI=00000000  EBP=00000000  ESP=09F7FFF4  EIP=00000000  FLG=00010202
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B
Error occurred at 8/30/2010 22:32:14.
C:\FreeFalcon5\FFViper.exe, run by CCC.
2 processor(s), type 586.
4063 MBytes physical memory.
OS: 6.1 build 7600 platform 2 
Version: Falcon 4.0 - Version 1.13.1.20422
FFViper : 2, 3, 3, 5
Card: DXContext::Init - DriverInfo - "atiumdag.dll" - "ATI Mobility Radeon HD 4570  ", Vendor: 4098, Device: 38227, SubSys: -1875701683, Rev: 0, Product: 0, Version: 0, SubVersion: 0, Build: 0

Game is Campaign type Local
DX Model ID : ffffffff
Texture ID  : ffffffff

[ccc]

after few "canShootWeapon" type CTD in 2d map, i kept running cam at 16x.

on Day 8 2350, one single armour unit finally captured P'yongyang by AI command. the war ended.

img]http://i112.photobucket.com/albums/n192 ... gooshh.jpg[/img]

[Hustler]

As I stated in another post...only Armor can capture an Objective and trigger a win.

on Day 8 2350, one single armour unit finally captured P'yongyang by AI command. the war ended.

[ccc]

PS- comment about movable GUs in cam..

older falcon cams have more "movable " GUs, so Blue ground power usually reach Hamhung at NE of Wonson, and Sunan at north of P'yongyang, then encircle p'yongyang for final offensive. Red side also have more movable GUs, so Red can maneuvor GUs to counter-strike the Blue offensive at Wonson and P'yongyang. I've seen hot battle at north of both key obj, blue fighting to counter DPRK reinforcement GUs.. BAI and CAS are cool mission there- intercepting DPRK reserves, PRC and CIS reinforcement.

In F5.5 cam i did not see such counter-strike..probably due to fewer movable GUs.
=============

As I stated in another post...only Armor can capture an Objective and trigger a win.

in my first F5.5 cam test - it's a HQ unit captured Wonson and ended the war.

[Hustler]

Then that Unit contained Armor. This is very clearly stated in the code.

As I stated in another post...only Armor can capture an Objective and trigger a win.

in my first F5.5 cam test - it's a HQ unit captured Wonson and ended the war.

[Hustler]

I was thinking of a better way to explain this. You refer to a HQ unit, the code see's 3-6-1-6-1. That number in our database is a land, unit, battalion, tracked_HQ, specific #1 (HQ M2A2 BCV). Contained within that Unit are vehicles like: 3-7-3-3-6, or a land, vehicle, tracked, tracked_armor, specific #6 (M1A2). Falcon is just a database, the common names are there for us but the code only uses the numbers. Add all the data used for the M1A2, all the flags, ACD entries, range, speed, crew, engine noise, etc used on this vehicle and now the M1A2 is a 3733649400227462543 (only an example). If any of these numbers are out of a range that is expected or defined, you have bad data. An example would be Radars..you only have 125 defined in the radar types list, but you have radar 126 assigned to an F-4E. There is no Radar #126 so your number is out of the defined range..bad data, possible crash. Make sense?

[demer928]

No,it does'nt make sense.
Please rewrite the post in Binary, so I can understand?????????


Just Kiddn'
demer