Page 1 of 1
Scenario Editor v5.2.9 Unit definition issue
Posted: Sat Feb 24, 2018 1:29 pm
by GabeKnight
Is it just me or is the "Unit definition" / "Unit Type" condition not working in the scenario editor since the v5.2.9 update anymore? Can't select no unit with left-click. Tested it with "Check Unit Count" and "Kills & Casualties"...
Or am I doing something wrong as I'm not that used to placing new units in the editor?
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Wed Feb 28, 2018 10:38 pm
by GabeKnight
No one else? Yes? No?
Experienced it trying to fix the
SU-122 "switch-bug" in the secondary objectives of the PK "Krakov 43" scenario.
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Fri Mar 02, 2018 11:54 am
by PoorOldSpike
GabeKnight wrote:No one else? Yes? No?..
I don't understand your question exactly mate so I can't run tests.
In fact I'm having trouble with the editor myself because none of the small scens I've created work!
I don't know if the 5.2.9 update is to blame, but after playing a few turns of my creations they freeze and/or the graphics break up and I get a fatal error message and have to go off for a cup of hot sweet tea and a lie down.
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Fri Mar 02, 2018 3:54 pm
by GabeKnight
Oh, okay, thought I was clear about it...

I mean selecting a unit with this or similar triggers doesn't work for me anymore:

- Screenshot 192.jpg (254.34 KiB) Viewed 1785 times
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Fri Mar 02, 2018 5:29 pm
by PoorOldSpike
I'd better sheepishly exit this thread mate because I've got as much chance of understanding the fiddly trigger system as I have of understanding women..

Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Fri Mar 02, 2018 7:48 pm
by terminator
The problem is that the SU-122 is a switchable unit.
With this example, the trigger only works with one type of SU-122 ART or AT(?).
If the AI switch the Unit type for the SU-122, the trigger will not work !
The two types of SU-122 should be incorporate in the Unit Definition :

- Su-122.JPG (17.06 KiB) Viewed 1777 times
I have this problem with my scenario Kursk soviet corps.
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Sat Mar 03, 2018 1:26 am
by GabeKnight
terminator wrote:The problem is that the SU-122 is a switchable unit.
With this example, the trigger only works with one type of SU-122 ART or AT(?).
If the AI switch the Unit type for the SU-122, the trigger will not work !
The two types of SU-122 should be incorporate in the Unit Definition :
Su-122.JPG
I have this problem with my scenario Kursk soviet corps.
So the trigger as such works for you? Strange. Maybe some rookie mistake on my side then.
Yes, the AT/ART switching is another matter, but I can't even change or choose a different unit, like a KV of infantry, to test an alternative solution for this scenario. Even creating new triggers doesn't seem to work.
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Sat Mar 03, 2018 10:59 am
by terminator
The trigger works for me.
I have reproduce the trigger in this small scenario :
Re: Scenario Editor v5.2.9 Unit definition issue
Posted: Sat Mar 03, 2018 3:47 pm
by GabeKnight
terminator wrote:The trigger works for me.
I have reproduce the trigger in this small scenario :
Thanks terminator!
I see now, a stupid beginner's mistake on my side. I'd click on the units on the map INSTEAD of the units of the roster.
Okay, but now that this is settled, lets go back to this one:
terminator wrote:The problem is that the SU-122 is a switchable unit.
With this example, the trigger only works with one type of SU-122 ART or AT(?).
If the AI switch the Unit type for the SU-122, the trigger will not work !
True, but as there are two different SU-122 versions in the units roster also, you can create trigger(s) for both variations. The unit's name looks the same in the trigger, but counts the different versions correctly. I've enhanced your test scenario that way, and it works.
That means, the only reason why the Panzerkrieg "Krakov 43" sec. objective still doesn't work right is 'cause the dev's just being sloppy again...

- Screenshot 193.jpg (113.32 KiB) Viewed 1737 times