strikeRadarUasge=2

All discussions & material related to Command's Lua interface

Moderators: RoryAndersonCDT, michaelm75au, angster, MOD_Command

Post Reply
User avatar
wqc12345
Posts: 176
Joined: Mon Dec 07, 2015 2:56 pm
Location: San Francisco, CA

strikeRadarUasge=2

Post by wqc12345 »

Hi All, this selector doesn't seem to work? Anyone have the correct number values for this setting?

If I want to set Active Radar from IP to Winchester? is this "1" ? If so, NO number works to change the value.. so, not sure if this is a bug? or something is missing

ScenEdit_SetMission(m.side, m.name,{strikeRadarUasge=2})
KnightHawk75
Posts: 1850
Joined: Thu Nov 15, 2018 7:24 pm

RE: strikeRadarUasge=2

Post by KnightHawk75 »

'StrikeRadarUsage' is the setting, case may matter, though I'm pretty sure it all gets converted to uppercase everywhere anyway.

The valid settings are (and case doesn't matter here):

"None" or 0
"UseMissionEMCON" or 1
"ActiveOnIP" or 2
"ActiveOnAttackIngressAndIP" or 3

You do need to feed it a type or subtype so it knows what type it's trying to do\check settings on, different types have different settings lists.
So for example and ScenEdit_SetMission('US', 'testmestrike',{SUBTYPE="Land",StrikeRadarUsage="ActiveOnIP"})
That will enable it to start checking and use the land and strike subtypes, otherwise it'll exit early unable to match a subtype.

After that though there is still an bug with this particular setting text that will require a tiny correction on devs part.

The problem is "StrikeRadarUsage" in one place, and "StrikeRadarUasge" in the list of strike entries to screen for in the first place. So you have a situation where if you feed it the "Usage" version it will not pass an initial test to even check the values, but if you feed it "Uagse" version it will pass the screening test, but then fail the deeper compare to actually check\change the setting as there is no match.

I don't think there is any work around at the moment for this particular setting till the spelling is corrected in the screening list.

edit: originally said just sub-type when I meant type and\or subtype.
User avatar
wqc12345
Posts: 176
Joined: Mon Dec 07, 2015 2:56 pm
Location: San Francisco, CA

RE: strikeRadarUasge=2

Post by wqc12345 »

Hi Knight, I fixed the spelling of the setting and tried again..(thanks, fail)

Code: Select all

local mission = ScenEdit_AddMission ( 'RAF', 'RAF Nairobi Strike', 'strike',{ type = 'land', TankerUsage=1})
 for i = 1, Count
 do
 ScenEdit_AssignUnitToMission(unitsToAdd[i], mission.name)
 end
 
 local m = ScenEdit_GetMission('RAF','RAF Nairobi Strike')
 ScenEdit_SetMission(m.side, m.name,{SUBTYPE="Land", StrikeRadarUsage='ActiveOnIP'})
 ScenEdit_SetMission(m.side, m.name,{strikeFlightSize=3}) 
 ScenEdit_SetMission(m.side, m.name,{strikeAutoPlanner=true}) 
 ScenEdit_SetMission(m.side, m.name,{strikePreplan=true}) 
 ScenEdit_SetMission(m.side, m.name,{strikeOneTimeOnly=true})
 ScenEdit_SetMission(m.side, m.name,{strikeRadarUasge=2})
 

This still doesn't work.. it won't change the setting.. so I'm assuming this is the "little" bug you're referring to? Even if I change it to "2" it won't work..
KnightHawk75
Posts: 1850
Joined: Thu Nov 15, 2018 7:24 pm

RE: strikeRadarUasge=2

Post by KnightHawk75 »

Hi Knight, I fixed the spelling of the setting and tried again..(thanks, fail)

You didn't understand, that's ok. It was more for when Michael likely sees the comment. [:)] This is not something you can fix with spelling in your code, it's a spelling error in the games code the developers have to fix which is why there is no workaround around for it at the moment.

User avatar
wqc12345
Posts: 176
Joined: Mon Dec 07, 2015 2:56 pm
Location: San Francisco, CA

RE: strikeRadarUasge=2

Post by wqc12345 »

ah, thanks..
User avatar
michaelm75au
Posts: 12465
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

RE: strikeRadarUasge=2

Post by michaelm75au »

Sorry about that...bad typing.

Will fix.
Michael
Post Reply

Return to “Lua Legion”