Re: [Flightgear-devel] The sun is rendered as rectangle?

[Tatsuhiro N. <tat...@ni...>]

Mark,

On Nov 19, 2006, at 11:47 AM, Mark wrote:
>
> I'm pretty sure it's not a problem with Simgear. After all the code  
> has
> been this way for 3-4 years.

Thanks. So I don't have to modify SimGear.


> I've had analog problems when developing the sun code in cvs.
> When there isn't a file for the texture or the file is defective, the
> texture is displayed as a solid square.
> Or it's filled with a red-white checkerboard (depending on platform).
> If you have Gimp, please take a look at
> <FG-base-dir>/Textures/Sky/halo.rgba and see if it's ok.

I already checked the texture of the sun, and it seems OK, as long as  
it's supposed to be a round-shaped white-centered gradation that has  
4 channels (RGB and alpha). I also checked if SimGear has the correct  
path for halo.rgba by using std::cout << path.c_str(), and it was  
correct.
So, I'm wondering either SimGear or PLIB doesn't read (or process)  
the file properly even though it is given a correct path.

I'm sure that orb works fine as I can see the sphere in the sky when  
I disable the halo in oursun.cxx.
Well, I'm going a bit deep about this issue.

> Also make sure your not using the data-package from cvs because the
> sun-textures were redone/renamed.

I tried both 0.9.10 base package from the web site and from cvs. Both  
are resulting the same in terms of rendering the sun.


> And of course the GL/GLUT versions should be up to date (which they
> probably are - didn't check that :-)

Apple's GLUT (3.3.9) is not the latest but I think it should be OK as  
0.9.9-ppc build uses the same GLUT and it renders the sun correctly.
There's a GLUT 3.7 package (darwinports), but it is for X11, which I  
don't like to use for FlightGear.


> Are there any errors on the console when running?

No, I see no errors so far. probably I should see any potential  
errors with --log-level=info or debug.

Tat

-------------------------------------------
Tatsuhiro Nishioka
Mail: tat...@ni...
-------------------------------------------