Sorry for doing another topic with same name. I don't know how to delete previous one.
So here it is:
Tested on several machines
Latest AC 1.86.1 Unity 6000.3.9 or 6000. 4.0
I have two Hotspots - 1 and 2. Hotspot2 has RememberHotspot component and initial state is OFF
Hotspot1 has Use Interaction with only one command: HotspotEnable and must turn ON Hotspot2. It doesnt work. This command is not even being highlighted with green as an active command. I added some other command AFTER HotspotEnable for testing, like setting a variable. And those commands work. So it is like I have HotspotEnable command skipped.
Sometimes it can work few times and then it doesn't work again.
The example above is made for test, but exactly the same happens in game's other actions. I tried to clean save files - doesn't help.
BUT
I created new clean project, added latest AC and created the same sample scene with 2 hotspots and it worked. So I was wondering what can happened.
https://www.dropbox.com/scl/fi/fcttuzns4ld7smtehf9f7/enable-hotspot.png?rlkey=5hv1sodpho3ghkgy4xvva9taz&dl=0
https://www.dropbox.com/scl/fi/rsinaeh4qw281a8dlmjjp/components.png?rlkey=5gs6kasbko0f8x5d61dk2se8i&dl=0
UPDATE:
We've found out, that on some machines action Hotspot:Enables sets Hotspot from IngoreRaycast Layer to DistantHotspot. Why can it be? Sometimes it sets Default layer and it's ok and sometimes DistantHotspot.
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
Another update, maybe helpful for someone.
In Setting, in Hotspot setting in Detection method you should select Player Vicinity. ONLY in this case you'll be able to see Place distant hotspots on separate layer? option and turn it off.
I suggest maybe make this option visible even when other detection modes are active.
Options show based on whether or not they have an effect. "Place distant Hotspots on separate layer?" should only have an affect when using Player Vicinity Hotspot detection.
Is this detection method being changed at runtime?
No, it wasn't changed at runtime. It was changed in Editor before running the game some time ago and then back to MouseOver.
I can repeat our steps so you can try by your own.
Set Detection method to Player Vicinity with "Place distant Hotspots on separate layer?" ON.
Set Detection back to MouseOver and there is a problem described above.
Then what we did:
we've changed (not at runtime) Detection to Player Vicinity, turned "Place distant Hotspots on separate layer?" OFF, changed Detection back to MouseOver and it worked,
So it looks like "Place distant Hotspots on separate layer?" option is being saved somehow when changing Detection Method.