[BUG] [Mapedit] Sector out of bounds problem

[Bloody-Tom]

Raze version

Raze 1.7.1

Which game are you running with Raze?

Blood

What Operating System are you using?

Windows 10

Please describe your specific OS version

Windows 10 Professional

Relevant hardware info

No response

Have you checked that no other similar issue already exists?

• I have searched and not found similar issues.

A clear and concise description of what the bug is.

When a moving sector (for example a sliding sector) starts in bounds and gets slided out and back in there is no problem.
For example I made this map to illustrate

But if you drag a moving sector out of bounds at the beginning of a map and start the map with the sector out of bounds (for example you want to exchange moving sectors) Raze can't handle it.
See picture no.2

If a map starts with a moving sector out of bounds it doesn't appear if it's moved back in bounds.

DOS, NBlood and GDX can handle this.

I added the examples of these maps so you can check it out for yourself.

https://www.mediafire.com/file/mr7o8kt3tyu2ayh/example_maps_moving_sectors.zip/file

Steps to reproduce the behaviour.

Explain how to reproduce

1. Play the eample maps
2. Activate the trigger
3. Observe the mobving sectors

Your configuration

No response

Provide a Log

No response

[coelckers]

Unfortunately this one's not easy to fix. to properly triangulate a sector the renderer needs to know which lines define a shape. In this case the map analyzer detects two separate shapes, and this is only run once on map start because it's too costly to do repeatedly.