Occlusion lines not intersecting again

[cwsoots]

I'm seeing the return of the issue of drawn occlusion (wall) lines not creating points when intersecting. See the linked video. I'm running the latest version, also shown in the video.

https://1drv.ms/v/s!Aocvbx1XzPmhnLBjk7puxAUVlz43vw?e=UchJFc

Following some additional editing on the same map, the lines once again would create intersections but I have no idea what the trigger was.

[Agathon]

I'm seeing the same thing.

Fantasy Grounds - v4.6.6 ULTIMATE (2025-02-20)

[LordEntrails]

Can you provides step to recreate? Or an example campaign? And you are not drawing the occluders on a different layer?

[pindercarl]

I'm seeing the return of the issue of drawn occlusion (wall) lines not creating points when intersecting. See the linked video. I'm running the latest version, also shown in the video.

https://1drv.ms/v/s!Aocvbx1XzPmhnLBjk7puxAUVlz43vw?e=UchJFc

Following some additional editing on the same map, the lines once again would create intersections but I have no idea what the trigger was.

Thanks for posting the video. Occluders are added to the visibility computer and stored as a "bucket" of segments. For performance, it's faster to check occluders against the segments in the visibility computer for intersections. If an occluder hasn't been added to the visibility computer, or the visibility computer has not been updated, then the intersections would not be detected. Watching the video, it seems less likely that there is an issue with the line that you are adding, but that the error is with the previous line. Can you think of anything different about the previous occluder? Maybe it was added from metadata, or something similar?

[Laerun]

Thanks for posting the video. Occluders are added to the visibility computer and stored as a "bucket" of segments. For performance, it's faster to check occluders against the segments in the visibility computer for intersections. If an occluder hasn't been added to the visibility computer, or the visibility computer has not been updated, then the intersections would not be detected. Watching the video, it seems less likely that there is an issue with the line that you are adding, but that the error is with the previous line. Can you think of anything different about the previous occluder? Maybe it was added from metadata, or something similar?

I have also seen this behavior in the past. To me, without any idea or knowledge of the map tools programming, it seems like it might be related to changes made between major updates, provided the tools were updated or worked upon. I cannot put my thumb on it, but perhaps it's also a Unity engine specific issue. So, if I created a map a couple months ago and then work on it again, it seems like these types of things occur. I have had this happen about three separate cases over the last couple of years. If I come across this behavior again, I will put more thought and research into this. For non-official modules, or such, one cannot easily revert to preserve older or the original changes like an updated and official adventure can.

[cwsoots]

Thanks for posting the video. Occluders are added to the visibility computer and stored as a "bucket" of segments. For performance, it's faster to check occluders against the segments in the visibility computer for intersections. If an occluder hasn't been added to the visibility computer, or the visibility computer has not been updated, then the intersections would not be detected. Watching the video, it seems less likely that there is an issue with the line that you are adding, but that the error is with the previous line. Can you think of anything different about the previous occluder? Maybe it was added from metadata, or something similar?

My best guess is that occluders were not creating intersections depending on how they were drawn (mouse and button click versus arrow keys and the + key). It still happens unpredictably but I haven't been able to recreate this issue reliably. I've been working on occluders over several different maps, both adding new occluders to new maps and modifying occluders on premade maps.

In response to your questions, the above case was me adding new occluders to a new map. The image/map was added by me and the occluders were all drawn within the same session, yet for some reason FGU wouldn't recognize an intersection of walls on lines that were drawn mere minutes apart.

I have seen some other map/image-related issues since then, but I haven't pursued a resolution yet pending further investigation or occurrences. I'll save those for another thread when I can capture them happening. If you're interested, other issues I've seen lately are:

I started drawing an occluder line, then chose ESC to cancel, which resulted in a new occluder line being created from my cursor and running off (to infinity?) to the upper left of the screen. This happened several times earlier this week, but I can't recreate it at this time.
Upon reopening a map I was just working on, the Fx layer labels were blank and the layers were unlocked after being labeled and locked moments earlier.

[Moon Wizard]

Carl provided a fix for this issue in the latest v4.7.3 release. Please run a new Check for Updates.

Regards,
JPG