Version: SU16 - 1.39.9.0
Frequency: Consistently
Severity: High
Context: Rangeview Airstrip (test build attached), while in devmode or community
Bug description:
I noticed that this has been fixed in 2024 (Or, at least as of SU2, I haven’t verified SU3), but the issue still persists in 2020.
If I do a Vector Placement line of an object that has LODs, LOD0 will be loaded for the first few objects near the starting node. However, as you go further down the line, it will change to the last LOD.
This means you can’t really do vector placement for any objects that include LODs, as the last LOD is usually pretty low quality, and thus can be seen up close with this bug.
LOD0
Just past the Windsock it changes to the last LOD
Attachments:
esd-airport-0aa5-rangeview.zip (289.0 KB)
(Requires Emerald Object Library to see cones)
I’ve seen a similar issue recently in FS24 (SU4)
Using vector placement to add perimeter fences (using MSFS Stock Objects). When using Vector Placement, render distances are very short, making it virtually unusable for perimeter fences.
The fence culls to the lowest poly LOD, which in the case of fences is nearly invisible. It does not seem to follow normal LOD curves.
This must be addressed, as Vector Placement is used extensively, particularly for perimeter fences
@Boris @FlyingRaccoon
Hello @Rotornut44
It’s very unlikely such MSFS 2024 fixes will be backported to 2020.
The bandwidth for MSFS 2020 is very limited so issues that are going to be addressed are going to be almost exclusively critical issues or stability related issues.
@vantech I have checked on MSFS 2024 using Fence_Grilling01_High object and couldn’t see any difference.
(VectorPlacement on the left, Scenery objects on the right)
If you still have an issue that you think is related, please create a dedicated report in the 2024 bug report section.
Regards,
Sylvain
