Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

??? #18

Open
AH-321 opened this issue Oct 23, 2022 · 15 comments
Open

??? #18

AH-321 opened this issue Oct 23, 2022 · 15 comments

Comments

@AH-321
Copy link

AH-321 commented Oct 23, 2022

What is going on here?
fgfs-20221022211712

@IAHM-COL
Copy link
Member

IAHM-COL commented Oct 23, 2022 via email

@langonginc
Copy link

I have the same problem and I removed -master of the folder.

image

@helijah
Copy link

helijah commented Dec 27, 2022 via email

@langonginc
Copy link

Check that the textures are indeed 24 bit. What you show is 99% the result of 32 bit textures for opaque objects. I've been explaining it since 2006 but no one is listening :(

I didn't get your point, can you tell me how to fix it?

@helijah
Copy link

helijah commented Dec 27, 2022 via email

@langonginc
Copy link

langonginc commented Dec 28, 2022

PNG or other textures are in 16777216 colors. Or 24 bits. 8 for red, 8 for green and 8 for blue. And for transparent images there is a fourth channel of 8 bit for transparency precisely Textures in 32 bit therefore. For everything that is opaque object, it is imperative to use 24 bit textures otherwise FG considers that there is transparency and that gives strange results. Unfortunately very often creators are not careful and use 32 bit textures anyway. And you were able to show the result with your photo. Classic.

Oh, I understand your meaning. But I modified all the png file depth to 24 bits, and it didn't work.

convert -depth 24 xxx.png ~/new/xxx.png

And I merged the folder.

cp -frp ~/new/* ./A350XWB

But...

image


Upd

I found this stuff displayed properly.

image

@helijah
Copy link

helijah commented Dec 28, 2022 via email

@IAHM-COL
Copy link
Member

@langonginc

I cannot replicate,
I launched the plane with latest commit, without altering the content, (ie pgn depth), and the external view launches appropriately in my box:
fgfs-20221228061055

@IAHM-COL
Copy link
Member

@langonginc

  1. Are you using https://github.com/FGMEMBERS/A350XWB/archive/refs/heads/master.zip
  2. what FG version?
  3. Any error log?

@langonginc
Copy link

  1. Are you using https://github.com/FGMEMBERS/A350XWB/archive/refs/heads/master.zip
  2. what FG version?
  3. Any error log?

I downloaded your link file and tried again, but it didn't work.

image

Flight gear version: 2022.3.17

I didn't found any error.

@langonginc
Copy link

Is my FG is too new? The plane cannot run in it?

@IAHM-COL
Copy link
Member

IAHM-COL commented Dec 31, 2022 via email

@ew10528
Copy link

ew10528 commented Sep 15, 2023

My apologies for necrobumping this issue, but this error is only reproducible on Mac machines. This is likely something to do with the MacOS version of FlightGear, as other aircraft such as the Boeing 787-9, which works fine on Windows, also experience the same texture bug on MacOS.
Screenshot 2023-09-15 at 8 01 59 PM

@ew10528
Copy link

ew10528 commented Sep 15, 2023

@langonginc It appears that the original version of the A350 (https://github.com/Sbyx13/A350XWB) works fine on MacOS. Consider using that instead (if you still play FlightGear, that is).

update: it doesn't function at all but the model loads fine, ig that's that
Screenshot 2023-09-15 at 8 07 05 PM

@IAHM-COL
Copy link
Member

That's interesting insight. I unfortunately don't have access to a macos
I can try updating the normals and send some changes but need to be verified if it actually is a fix on macos
Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants