[sp / CO-OP MP] EXPANSION - a Dynamic Mission and Sandbox (all aircraft)

[Dangerzone]

3 hours ago, Grindmetal said:

i miss playing this mission
ED help us fix these problems soon please

I agree that it would be good to have this resolved by ED. However, you could play the mission now if you want, by rolling back to version 2.9.5.55918 until ED has this resolved. Not ideal - but it is an option.

[GrEaSeLiTeNiN]

Solo play issue: After a zone is captured and turned blue, the FARP appears with trucks but no aircraft. Consequently, I could not enter any aircraft in the slot I picked for that zone. Message says "currently blocked and can't be entered" even though the zone is blue. Also cannot enter any aircraft spawned via Olympus. 

Edited August 22, 2024 by GrEaSeLiTeNiN

[DD_Friar]

I have replaced my ownedZones with invisible farps and am using the standard DCS capture rules (which have a hierarchy in case you did not know, capture works if a controlling force has the zone, you do not have to kill ALL enemy units. For example a red zone occupied by troops and you roll blue armor into town you will take the zone without killing the troops.)

[cfrag]

1 hour ago, GrEaSeLiTeNiN said:

Solo play issue: After a zone is captured and turned blue, the FARP appears with trucks but no aircraft. Consequently, I could not enter any aircraft in the slot I picked for that zone. Message says "currently blocked and can't be entered" even though the zone is blue

That is strange, even with the bugs in DCS. Did you in any way customize the mission? It looks as if cfxSSBClient is failing to free the slots when the FARP is captured. 

[GrEaSeLiTeNiN]

4 hours ago, cfrag said:

That is strange, even with the bugs in DCS. Did you in any way customize the mission? It looks as if cfxSSBClient is failing to free the slots when the FARP is captured. 

Well, I did use Olympus to capture the zone by spawning blue units in it once all red hostiles were eliminated. The blue units spawned by Olympus disappear in the next mission leaving only the blue units created by Expansion's scripts such as the FARP trucks and the Roland SAM, but no aircraft is present.  Even the aircraft spawned by Olympus is prohibited from being flown by the player. It's like there is a blanket prohibition from flying any aircraft that is not from Nalchik.

Edited August 7, 2024 by GrEaSeLiTeNiN

[cfrag]

18 minutes ago, GrEaSeLiTeNiN said:

The blue units spawned by Olympus disappear in the next mission leaving only the blue units created by Expansion's scripts

Ah, so you are saying that the player blocking problem appears after a mission reload, not during normal mission flow, and it happens after the capture was made by units that the mission does not know about (and thus cannot track). It makes sense in a weird way, as on mission re-load with persistence (since there is no 'real' persistence in DCS), re-constructing the correct owner fails, and the FARP enters a limbo state. Not really captured (it probably starts neutral in the mission), but the persisted FARP insists on blue owner. Does this issue also occur when not using units spawned from Olympus?

[cfrag]

56 minutes ago, GrEaSeLiTeNiN said:

It's like there is a blanket prohibition

Pleas try the patched FARP script. It should restore spawn ability, but ONLY after the first 10 seconds of the mission have progressed. DCS, SSBclient and the mission require this 10 second interval to communicate who owns what.

FARPZones.lua

Edited August 7, 2024 by cfrag

[GrEaSeLiTeNiN]

Ah, so you are saying that the player blocking problem appears after a mission reload, not during normal mission flow, and it happens after the capture was made by units that the mission does not know about (and thus cannot track). It makes sense in a weird way, as on mission re-load with persistence (since there is no 'real' persistence in DCS), re-constructing the correct owner fails, and the FARP enters a limbo state. Not really captured (it probably starts neutral in the mission), but the persisted FARP insists on blue owner. Does this issue also occur when not using units spawned from Olympus?

I’ll have to try without Olympus but as a solo player, I don’t know how to put units in the zone to capture it. I looked at the F10 menu but there does not seem to be an option for those kinds of actions. What is strange is that the FARP vehicles appear after capture (with Olympus) but without any helos. I think that’s why picking a slot from that FARP can’t work whether during the mission or when starting a new mission.

[cfrag]

Just now, GrEaSeLiTeNiN said:

What is strange is that the FARP vehicles appear after capture (with Olympus) but without any helos.

I believe that is a synch issue between SSBClient and FARP. Have you had the opportunity to try the new script (drop-in replacement)? It should work with saved missions and allow to use player slots in captured FARPS after 10 seconds mission run time.

[GrEaSeLiTeNiN]

10 hours ago, cfrag said:

I believe that is a synch issue between SSBClient and FARP. Have you had the opportunity to try the new script (drop-in replacement)? It should work with saved missions and allow to use player slots in captured FARPS after 10 seconds mission run time.

Ehh.. sorry but how do I use the new script? Where do I place the lua file? Thanks

[cfrag]

11 hours ago, GrEaSeLiTeNiN said:

how do I use the new script?

My apologies, I forgot that changing scripts isn't something people in general are comfortable with, nor should they. I'll update the mission and as soon as we have a new DCS release I'll try to asap push out an update that includes this change. 

[GrEaSeLiTeNiN]

16 minutes ago, cfrag said:

My apologies, I forgot that changing scripts isn't something people in general are comfortable with, nor should they. I'll update the mission and as soon as we have a new DCS release I'll try to asap push out an update that includes this change. 

Ok, thanks very much for looking into this!

[Grindmetal]

Update fix mission?

[WipeUout]

Been playing for a couple of hours and all seems good so far.

[Grindmetal]

yes apparently it's ok as before, no errors in the logs or helicopter spawn problems 

 

I'll keep the server running and report any errors to cFrag.

 

@cfrag in the future add a RANK system or Xp touch Roleplay would be cool in it

Edited August 10, 2024 by Grindmetal

[WipeUout]

A few issues:

Getting double A2A kill points.  I get notification for points earned when airplane is killed and again when the downed airplane body crashes on the ground.  Although nice to get 150 points instead of 75, not sure this is intended nor if related to DML or DCS.

Other issue is with stopGap.  Although disabled through the config trigger zone, it activates back if I go into slot select, then hit cancel, then re-select blue faction. 

[cfrag]

10 minutes ago, WipeUout said:

Getting double A2A kill points. 

Ha! Good catch, thank you! Yes, another wonder of the new release. I'll see what I can do.

[phrogZ]

I read somewhere ( don't remember where ) there is a new bug: with both S_EVENT_KILL, onGameEvent('kill').

 

EDIT: It was on SpecialK discord:
"There is a big issue in the latest ED patch. We do get doubled S_EVENT_KILL and onGameEvent('kill') events now"

Edited August 10, 2024 by phrogZ

[cfrag]

15 minutes ago, phrogZ said:

there is a new bug: with both S_EVENT_KILL, onGameEvent('kill').

It would seem so, yes. The internal code will not count kills double, this must be tied to the new event oddities (there are many, some involving kills, some landings, and distributed over platforms: single-, multi-player, dedicated). What a mess. 

[Grindmetal]

wow they seem to be killing the game hahahahahaha

[Dangerzone]

On 8/10/2024 at 9:14 PM, cfrag said:

It would seem so, yes. The internal code will not count kills double, this must be tied to the new event oddities (there are many, some involving kills, some landings, and distributed over platforms: single-, multi-player, dedicated). What a mess. 

Time to ask ED for a bug fix only release maybe.  No enhancements. No new functions. Just dedicated the entire next release cycle to bug fixing. Both the new ones and others that have been outstanding for years. Because honestly, this OB/SR migration it seems is turning back into OB instability with a longer release cycle. 

Edited August 12, 2024 by Dangerzone

[phrogZ]

FYI dedicated server is still crashing with SSB :
 

2024-08-13 20:50:46.082 ERROR   SCRIPTING (Main): Mission script error: [string "cfxSSBClient = {}..."]:297: attempt to call method 'getLife' (a nil value)
stack traceback:
	[C]: in function 'getLife'
	[string "cfxSSBClient = {}..."]:297: in function 'onEvent'
	[string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>
	[C]: in function 'force_player_slot'
	[string "stopGap = {}..."]:286: in function <[string "stopGap = {}..."]:276>

 

Edited August 13, 2024 by phrogZ

[eric963]

Same error on my dedicated server tonight also.

[cfrag]

10 hours ago, phrogZ said:

FYI dedicated server is still crashing

Thank you. This is one of the bugs introduced with the Jul-11 DCS release and requires an update to Expansion that I hope to be able to release soon.

 

Edited August 14, 2024 by cfrag

[phrogZ]

Thanks for all the great work, really appreciate it!