the 1.4prev9 bug report thread

[brokfn]

- I did download complete 1.4.0pre9
- I did check the galaxy rendering box
- galaxy templates are in th emodels directory.

Bye, Brokfn

[t00fri]

- I did download complete 1.4.0pre9
- I did check the galaxy rendering box
- galaxy templates are in th emodels directory.

Bye, Brokfn

Very strange. I am mainly surprised why you don't seem to see galaxies. Did you see galaxies with your card in any previous release, e.g. FT1.2 ??

If you do not use the Automag (CTRL+y) you must turn up the limiting magnitude with the "]" key to something like 8.0-9.0. If you type M 31 <return> into the command line, followed by 'c' (center), do you see the label M 31 after toggling the galaxy labels=ON ('E' key)?

Bye Fridger

[selden]

As mentioned previously, I also get the 2.0->Basic render path crash: "unhandled Win32 exception: Access violation reading location 0x00000000". I verified that ell_galaxy_arb.vp exists, dated 10/7/2005. (October 7th)

System:
1GB, 3.4GHz P4-550; WinXP Pro SP2
128MB GF 6600 GT; ForceWare 81.87
Celestia v1.4.0 pre9

When I build Celestia from CVS, that version doesn't crash, but I'm sure there are plenty of differences between how I build Celestia from CVS and how Chris builds it for distribution.

FWIW, comparing Win pre9 with the CVS shaders folder, I found 2 shader files that aren't included in pre9: sample_nv.fp and star_arb.vp, but adding them to pre9 makes no difference. Copying the CVS version of ell_galaxy_arb.vp doesn't help, either.
*sigh*

[brokfn]

Actually, I didn't test the previous releases on my ATI machine.
Galaxies are there, but appear extremely faint, even when automagnitude is set on.
I have to set the light gain to about 20% to see something comparable to my laptop.
By the way, Celestia doesn't seem to remember this setting when I quit, so I must set it each time I start the software : rather boring.

Nag a gudenno?? !

Bye, Brokfn

[t00fri]

As mentioned previously, I also get the 2.0->Basic render path crash: "unhandled Win32 exception: Access violation reading location 0x00000000". I verified that ell_galaxy_arb.vp exists, dated 10/7/2005. (October 7th)

System:
1GB, 3.4GHz P4-550; WinXP Pro SP2
128MB GF 6600 GT; ForceWare 81.87
Celestia v1.4.0 pre9

When I build Celestia from CVS, that version doesn't crash, but I'm sure there are plenty of differences between how I build Celestia from CVS and how Chris builds it for distribution.

FWIW, comparing Win pre9 with the CVS shaders folder, I found 2 shader files that aren't included in pre9: sample_nv.fp and star_arb.vp, but adding them to pre9 makes no difference. Copying the CVS version of ell_galaxy_arb.vp doesn't help, either.
*sigh*

Thanks, Selden,

that's useful info. But did you get that crash also with our FT1.2? My suspicion is still that Chris forgot to wrap in some (shader?) file into pre9, the lack of which now causes the crash.

Bye Fridger

[selden]

FT1.2 has no problems switching from 2.0 to Basic.

[t00fri]

I just tried it again:

Using a complete, fresh download & install of Celestia-1.4.0pre9...

My FX 5900Ultra driver is 78.01. I use 1280x960/32bit color, NO special settings in the NVIDIA driver GUI.

I tried with Earth and with Saturn centered and cycled through the render paths, everything remains fine, no crashes whatsoever between OpenGl 2.0 and Basic!

So I cannot do any further tests, since I am unable to provoke the crash

Also I do NOT get any incorrect renderings.

...Oh, here are some 'second' thoughts: did those who experience crashes carefully eliminate FT1.2 (or other previous releases) from the registry, since unlike FT1.x, Chris' installer does not coexist peacefully with other Celestia versions...

Bye Fridger

[selden]

I deleted all references to FT1.2.
pre9 still crashes.

[t00fri]

I deleted all references to FT1.2.
pre9 still crashes.

Is there an entry in shaders.log?

[selden]

I've been using the desktop icon to start Celestia. pre9 isn't creating shaders.log on the desktop. It creates an empty shaders.log in the Celestia folder. (Yet another bug?)

When I use the icon that's in the Celestia folder, shaders.log is created in the Celestia folder, but the file is truncated prematurely. Presumably the output buffer isn't flushed when Celestia crashes.

As best I can tell, though, the message is related to the "red earth" bug in the current Nvidia drivers. For various reasons, I'm reluctant to install the older drivers.

The last few lines are

Code: Select all

BB1:
DP3   R0.x, vertex.normal, c[4];
MAX   R0.x, R0, c[5];
MUL   R1.xyz, R0.x, c[6];
ADD   result.texcoord[0].xyz, R1, c[7];
DP3   R0.y, vertex.normal, c[8];
MAX   R1.xy, R0.y, c[5].x;
ADD   R0.y, R0.x, result.texcoord[3].x;
ADD   R0.y, -R0, c[5];
MOV   R1.z, c[9].x;
LIT   R0.z, R1.xyzz;
MUL   R0.x, R0, R0.z;
MUL   R0.w, R0.y, R0.y;
MUL   R0.z, R0.w, R0.y;
MAD   result.texcoord[4].xyz, R0.x, c[10], result.texcoord[4];
MUL   result.texcoord[3].x, R0.z, R0.y;
MOV   result.texcoord[2].xy, vertex.texcoord[1];
MOV   result.texcoord[0].w, c[5].y;
ADD   result.texcoord[1].x, vertex.texcoord[0], c[11];
MOV   result.texcoord[1].y, vertex.texcoord[0];
DP4   result.position.w, vertex.position, c[3];
DP4   result.position.z, vertex.position, c[2];
DP4   result.position.y, vertex.position, c[1];
DP4   result.position.x, vertex.position, c[0];
END
# 23 instructions, 2 R-regs
Vertex shader source:
  1: un


[selden]

Pre9 also crashes if I GoTo Mars and then step through the render paths. A 0K shaders.log is created when Celestia is started using the icon that's in the Celestia folder.

The "red globe" driver bug isn't seen when viewing Mars, so I don't think the crash bug is related to the renderpath/driver problem.

[cartrite]

This morning 1.4-pre9 crashed every time I switched from opengl 2.0 to basic. I tried to find the error report that Windows reported to make but could
not find it. So I uninstalled 1.4-pre9. After reading the above posts I reinstalled it and the crash disappeared.
Now some notes.
I looked into the registry and the only reference I find is in current user\software\shatters\celestia. There does not seem to be any settings that are FT1.2 specific. I do have an atypical install tho.

1st I have 1.3.2 installed from a former Windows OS that was uninstalled long ago. 1.3.2 is installed on it's own 20 GB partition. That is were the main extras folder is. All other Celestias make reference to it via the celestia.cfg file.

2nd The only Celestias that are installed via a windows installer are 1.4-pre6,7,9. The FT's and CVS versions are not installed. They were built and I run them from the folders they were built in. When I first installed pre6 I put it in the default location. Thats C\Program Files\Celestia. The other two are in their own folders on different partions. I don't know if this makes any difference. I seem to have no problems at the current time. Now I can't reproduce the ctrl+v crash with 1.4-pre9.

I only added my driver info because thats my hardware and software.
In case this bug is hardware or software specific.

One other thing. FT-1.2 and the CVS versions don't display level 11 or 12
textures. 1.4-pre6,7,9 do. That's by design I guess?

cartrite

[cartrite]

I don't know what these settings were when 1.4-pre9 was crashing but these are the only settings that seem relevant.
Hkey_Current_User Software Shatters.netRenderFlags0x00049797(300951)
Hkey_Current_User Software Shatters.netLastVersion0x01020500(16909568)

cartrite

[selden]

Unfortunately, reinstalling the full pre9 kit from scratch didn't eliminate the crash for me. I can't find any registry entries like the one cartrite describes.

Oh, well, enough beating of this dead horse...

[selden]

I finally persuaded pre9 not to crash.

I deinstalled Celestia 1.4.0pre9 using the Windows Control Panel/ Add-Remove programs menu. Reinstalling made no difference: it still crashed.

I deinstalled Celestia 1.4.0pre9 by using the uninstall utility's icon in the Celestia folder. Reinstlaling this time did make a difference: now it does not crash.

Confusion abounds.

[t00fri]

I finally persuaded pre9 not to crash.

I deinstalled Celestia 1.4.0pre9 using the Windows Control Panel/ Add-Remove programs menu. Reinstalling made no difference: it still crashed.

I deinstalled Celestia 1.4.0pre9 by using the uninstall utility's icon in the Celestia folder. Reinstlaling this time did make a difference: now it does not crash.

Confusion abounds.

But I am sure it's related to the registry entries...

Once more: victory by persistence

Bye Fridger

[cartrite]

I failed to mention something strange that may have something to do with this. When I first installed 1.4-pre6 there was a listing in Control Panel / Add Remove Programs that said Celestia. When I installed 1.4-pre7 that listing was replaced with a listing for 1.4-pre7. It said pre7 Celestia. When I installed 1.4-pre9, the pre7 listing was replaced with pre9 Celestia in Add Remove Programs. When I uninstalled 1.4-pre9 only 1.4-pre9 was uninstalled. Then there was no listing for Celestia at all. Both were still on my computer.

As far as the registry is concerned, All the entries that "I have" seem to have only a single purpose. That is to save the settings that were being used when the program was shut down. So they will be loaded when the program starts up. No matter what version of Celestia I use, The same settings are loaded from the previous session. I have no other reg entries for Celestia that I can find.

cartrite

[Vincent]

Something strange :

- I could reproduce the "Control-V crash" changing from the OpenGL Vertex/Nvidia Combiners mode to the Basic mode on my machine. (XP, Nvidia Geforce 4 MX, drivers v81.95)
- I did the same uninstall (from Celestia Folder) / reinstall than Selden did, and I had the same result : no more crash
- Then I replaced the data, textures, extras, models, and fonts folders with my personal ones (deleted the default ones, copied my personal ones) , and did the same with my demo.cel, start.cel, celestia.cfg, favorite.cel, guide.cel files.

And I got the "Control-V crash" back...

[cartrite]

Fridger seems to be right about the registry. The crtl+v crash started again.
Every time I changed from opengl 2.0 to basic. I saved the bad registry. Then uninstalled 1.4-pre9. Reinstalled it. Crash was gone again. Then I deleted the registry and imported the bad one. The crash came back. I'm going to try to see what entry is getting corrupted. I noticed that after it started crashing again, The RenderFlag entry changed. When I tried to change it back to the entry that worked It still crashed. Something else?

cartrite

[Vincent]

Ok, I replaced one by one all the files and folders I mentioned in my previous post. I found out that the file that is causing the "Control V bug" is my personal start.cel :

Code: Select all

{
#****************************************************************************
#                                                                           *
#                 START.CEL - Startup script for Celestia                   *
#                             (version 2.1)                                 *
#                                                                           *
#---------------------------------------------------------------------------*

cls {}
unmarkall {}

set { name "StarStyle" value "points" }

set { name "AmbientLightLevel" value 0 }

set { name "FOV" value 27.5 }

renderflags { clear "boundaries|constellations|grid|markers|orbits|ringshadows"}
renderflags { set "atmospheres|automag|cloudmaps|comettails|eclipseshadows|galaxies|planets|nightmaps|stars"}

labels { clear "asteroids|comets|constellations|galaxies|moons|planets|spacecraft|stars"}

unmarkall {}

preloadtex { object "Sol/Earth" }
preloadtex { object "Sol/Earth/Moon" }
wait   {duration 3}

timerate {rate 1.0}
cancel{}

select {object "Sol/Earth"}
setsurface { name ""  }
follow {}
goto   {time 5.0  distance 6.0}
wait   {duration 5}
}


Cartrite, we may have to find the link between my start.cel file and the registry problem...