Severity:Blocker
High - critical but workarounds are available, important feature not working as Marketplace package name: EDAQ
Bug description: scripted triggers don’t react anymore to the user when in walking mode (in previous alpha iteration it was working
Worst, scripted moving platform doesn’t work too (when moved with activatewaypointaction, the platform move while the helicopeter stay in place)
Repro steps: in EDAQ from Marketplace, spawn inside DRF hangar (west- N parking 0) and trigger the action by setting Lighting_Landing_1 to one (was landing light switch in the cabri in fs2020)
This is our NZWF on marketplace at NZOG. Same with NZTG Package at NZJA.
And also World Update 12 NZTL Hangar closest to the terminal which we made and added to the community folder for testing this. All using the same system, but not working now.
Theres also no info on this debug tool, because at NZJA its goes from green to blue. Unsure what the colours in the Debug World Object should represent.
Maybe this we need adjusting to another type or removing, or the player avatar code has changed? Would be great if Asobo can change it back to make it work like in previous builds, would be good for existing 2020 stuff.
<ObjectFilter>User</ObjectFilter>
“ObjectFilter - This can be one of: User, Reference or Anything.” From P3D mission editor tools help.
MSFS SDK has limited documentation on this.
Edit: Tried setting it to “Anything” Doesn’t fix it. Tried removing all together its the same.
@FlyingRaccoon Any update on this? For a sim with an avatar mode, we really need to get our hangar/terminal doors working. As far as i know the rectanlge triggers still arent working.
I have talked to our Lead Gameplay Programmer and we’ll try to have a look at this in the coming days - I have a feeling we will need to do something similar to what we did with SimConnect.
Depending on their needs, developers will sometimes need to access the user aircraft, the user avatar, or whatever the current user object is (aircraft OR avatar). In SimConnect we did this by introducing new special IDs (USER_CURRENT, USER_AIRCRAFT, USER_AVATAR) and I suspect we’ll need to do the same thing for the ObjectFilter. If we do so, USER will map to USER_AIRCRAFT as I believe it did in MSFS 2020 (I need to double check this though - if USER actually meant “Camera Position”, then it means that USER_CURRENT would be a better mapping).
Hopefully we can address this for SU2 (it is a bit too late for SU1, apologies for this).
Another suggestion could be to implement the ObjectFilter itself
Actually the ObjectFilter set to Anything should react to any Simobject, so why not the avatar?
And in the meantime, can you document the “reference” feature of the ObjectFilter?
Because e.g. I have some AI trucks (livingworld)moving in the airport, and I want them to open some gates. With ObjectFilter set to Anything the script triggers, but it triggers to much, because it reacts to terrain changes too (the one we get when zooming in and out), so wonder is it possible
A) that Anything should be related to every Simobjects, nothing else
B) if the reference thing is working, how can we implement it to only a list of specific Simobjects
@EPellissier@Boris any update on this. Can we please please get this fixed for SU3, we’ve been waiting for this one since release. I’ve had to release two products without this feature. Really don’t want to do it a third time.
