Please, help me!
FlightGear Forum
Board index ‹ FlightGear ‹ Support ‹ Graphics
Trees
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.
- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).
- please upload a screenshot of the problem.
If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you are seeing corrupted/broken textures, please see this article.
Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.
- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).
- please upload a screenshot of the problem.
If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you are seeing corrupted/broken textures, please see this article.
Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.
3 posts
• Page 1 of 1
Re: Trees
by erik » Mon Apr 19, 2021 9:28 pm
I've noticed the same for Open Street Map trees in Project 3000. I think it was referencing a missing texture.
But now with OSM2City support I do not use Project 3000 anymore.
Erik
But now with OSM2City support I do not use Project 3000 anymore.
Erik
Current: Parachutist, Paraglider, Pterosaur, Pilatus PC-9M and variants, ERCO Ercoupe, Fokker Dr.1, Fokker 50, Fokker 100
Less active: Cessna T-37, T-38, Santa Claus. Previous: General Dynamics F-16. Worked on: Wright Flyer
Less active: Cessna T-37, T-38, Santa Claus. Previous: General Dynamics F-16. Worked on: Wright Flyer
- erik
- Posts: 2248
- Joined: Thu Nov 01, 2007 2:41 pm
Re: Trees
by ludomotico » Mon Apr 19, 2021 11:22 pm
It seems this happens to some users after activating anti-aliasing in the launcher: viewtopic.php?f=37&t=37860
Try switching anti-aliasing off in the launcher. If you really want to fly with anti-aliasing, try the settings in the nVidia panel (if you have a nVidia card) and not the launcher. Please, tell us if any of this fixed your issue.
Try switching anti-aliasing off in the launcher. If you really want to fly with anti-aliasing, try the settings in the nVidia panel (if you have a nVidia card) and not the launcher. Please, tell us if any of this fixed your issue.
-
ludomotico - Posts: 1269
- Joined: Tue Apr 24, 2012 2:01 pm
- Version: nightly
- OS: Windows 10
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest