[SU2 Beta] Apron UV Offset Shifted

[Rotornut44]

Version: 1.4.9.0

Frequency: Consistently

Severity: High

Marketplace package name: 8AK5 Fort Crosby

Bug description:

I’m not entirely sure if this is a bug, or just a consequence of this fix noted in the SU2 release notes:

• Fixed apron UV shift when the generic airport position has moved between MSFS2020 and MSFS2024

This is the only reference I can find towards anything apron UV related.

I adjusted UV offsets to a lot of my aprons while redoing my airports in SU1, however now in SU2, all of that has shifted substantially.

I suppose I would like to know if this is intentional or not. If it is a bug that will be fixed, I’m not going to worry about putting any time into trying to replicate the offsets again. If it is not a bug and will be kept then I will have to make a lot of adjustments I suppose…

SU1

SU2

Ignore the darker dirt patch overlays. Those are not correct as well, but I took both screenshots in SU2 just replicating the main dirt offset exactly as it is in SU1 for the example.

[MichaelWimma-RWProfiles]

Bug has been there since the Dev alpha and the attempt to fix it in SU2 broke it even more unfortunately.

Shifting UV Maps of Aprons in 2024

Version: 1.1.9.0 Frequency: Consistently Severity: Blocker Marketplace package name: RW Profiles KSGF Springfield Branson Context: Place 2020 package nn 24 community folder Similar MSFS 2020 issue: Not an issue in 2020 Bug description: UV maps are shifted and not alingned to where they should be. This causes double lines, and can show unwanted other textures which are on teh same UV Map Repro steps: Place 2020 package in 24 community folder Attachments: In 2020 [FlightSimulator_ZpAfx…

@MichaelWimma-RWProfiles

unfortunately, I have to report that this got even worse with SU2 and is now so bad that it completely breaks the whole scenery!

This needs to be fixed or reverted back before public release, please! If it releases in this state our product will become unusable.

[Rotornut44]

Thanks for the links! Unfortunately that probably means I am redoing them either way at some point in the future.

[MichaelWimma-RWProfiles]

Well if it’s a 24 project then ofc “no problem” as you could in theory re-do them. (for small airports maybe but if you’d have to changed that for big airports then yeah not great just saying… (especially if you have a few to change haha))

But in this case, since it’s a 2020 project, their position can’t be changed because then it would obviously break the 2020 version. So in either case this must be reverted back to what it was of, even better, fixed completely.

[Boris]

Hello,

@MichaelWimma-RWProfiles @Rotornut44
It’s fixed in the current flighting 1.4.11.0

Can you confirm ?

Note that there is still an ongoing issue that is currently being worked on.

[MichaelWimma-RWProfiles]

Affirm, we just checked

Thank you!

But it is still not completely fixed I want to add that.

It is now back to where it was before SU2, which is at least usable, but it is still not as it was designed in 2020.

[Boris]

@MichaelWimma-RWProfiles

But it is still not completely fixed I want to add that.

Yes, this is why I added this in my post above :

@Boris

Note that there is still an ongoing issue that is currently being worked on .

Regards,
Boris

[Rotornut44]

Interestingly, I do not see any change on my end in 1.4.11.0. I just compared with my SU2 photo above. I had someone on the SU1 stable branch double check for me as well and all of the screenshots I took of their screen are different from what I have now in SU2, but are the same as what I have shown in my SU1 screenshot.

Just for clarification, my package is 2024 native, so maybe this fix was only something applied for 2020 packages?

[MichaelWimma-RWProfiles]

Oh sorry Boris. I must have over read that! My bad. Apologies.

[Boris]

We checked again your issue, as it’s not the same as the one reported by other third-party developers.

The fact is, this behavior is by design:

Before SU2, the UV position was calculated relative to the generic airport coordinates.

Now, the UV is calculated relative to the specific airport it was created for.

This change helps prevent UV offset issues for custom airports, especially when the coordinates of generic airports change in future updates.

Note that the “local uv” option can be also used to “freeze” the coordinates of the UV.

Regards,
Boris

[Rotornut44]

Gotcha. I just ended up sitting down this morning and went through and manually adjusted all of the offsets to match what they were in SU1 again. Luckily I only had a dozen or so aprons to do.