Bugs in 1.4.0 final

[t00fri]

With my new 8178 Linux driver, I use

1) main texture
2) clouds texture
3) normal map
4) clouds texture
5) nightlights

in case of Earth without bad effects.

Bye Fridger

[cartrite]

I don't think I had any problems with the Linux driver 8174 in Celestia. It produced strange things with my system as a whole so I went back to 7676. I'm going to try this 8178. The Nvidia site says they fixed some kernel module problems with this release.

I had a lot of problems with the newer drivers for Windows in Celestia.

Fridger, Did you see the post I did earlier tonight on the previous page of this thread. You seemed to be asking how to change the month in the date menu.
You can use the arrow keys and the tab key to navagate and change settings thru the menu.

cartrite

[PlutonianEmpire]

Any idea when 1.4.0 will be available for download at the main celestiaproject.net/celestia site? Just curious.

[cartrite]

I found it at :

http://sourceforge.net/project/showfile ... p_id=21302

cartrite

[t00fri]

...
Fridger, Did you see the post I did earlier tonight on the previous page of this thread. You seemed to be asking how to change the month in the date menu.
You can use the arrow keys and the tab key to navagate and change settings thru the menu.

cartrite

OK thanks, cartrite, you are of course right. The date fields (including th month) may be changed with the up/down cursor keys.
Yet in the date line, the selected field is NOT inverted, such that I can't see what I am dialing...

Bye Fridger

[jdou]

About the NVIDIA driver 81.98

On my PC, the last version of Celestia 1.4.0 works well.
No longer red Earth ?????

Happy Christmas and Happy new Year

[Fightspit]

I can confirm that the problem with ATI cards are solved with 1.4.0 final .(I hope )
It work with the X700 mobility in my notebook.

Comme le dit jdou:

Joyeux No?«l et Bonne Ann?©e 2006 ?  Tous

[cartrite]

I was looking into the CVS code for windatepicker.cpp (which has the same date problem. I found that if you make the following simple changes to the code the text gets inverted. The changes are marked red.

code
...
...
void
DatePicker::redraw(HDC hdc)
{
...
...
...
SetTextColor(hdc, RGB(0, 0, 0));
if (i == selectedField && haveFocus)
{
RECT r = fieldRects[i];
r.top = (clientRect.bottom - size.cy) / 2;
r.bottom = r.top + size.cy + 1;

HBRUSH hbrush = CreateSolidBrush(GetSysColor(COLOR_HIGHLIGHT));
FillRect(hdc, &r, hbrush);
SetTextColor(hdc, RGB(255, 255, 255));
DeleteObject(hbrush);

}
...
...
...


I tried to get an up/down button on the right hand side but could not get it to work or even appear for that matter. Too bad this is too late for the final but it works with the latest CVS which has the same date menu problem.

cartrite

[cartrite]

If people out there really can't see the date in the date menu there is a simpler soulition. One could right-click on their desktop and chose Properties/Appearance and set the Color scheme to silver. That's with XP.

cartrite

[Fightspit]

Other bug on Opengl 2.0 with ATI X700 Mobility (and others ATI graphic cards I think) in my Notebook with the lastest drivers.

The problem is only eclipse shadow:

Before:


After:


OpenGl info list:

Code: Select all

Vendor: ATI Technologies Inc.

Renderer: MOBILITY RADEON X700 x86/SSE2
Version: 2.0.5523 WinXP Release
Max simultaneous textures: 8
Max texture size: 2048
Point size range: 1.000000 - 64.000000

Supported Extensions:
GL_ARB_multitexture
GL_EXT_texture_env_add
GL_EXT_compiled_vertex_array
GL_S3_s3tc
GL_ARB_depth_texture
GL_ARB_fragment_program
GL_ARB_fragment_program_shadow
GL_ARB_fragment_shader
GL_ARB_multisample
GL_ARB_occlusion_query
GL_ARB_point_parameters
GL_ARB_point_sprite
GL_ARB_shader_objects
GL_ARB_shading_language_100
GL_ARB_shadow
GL_ARB_shadow_ambient
GL_ARB_texture_border_clamp
GL_ARB_texture_compression
GL_ARB_texture_cube_map
GL_ARB_texture_env_add
GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar
GL_ARB_texture_env_dot3
GL_ARB_texture_mirrored_repeat
GL_ARB_transpose_matrix
GL_ARB_vertex_blend
GL_ARB_vertex_buffer_object
GL_ARB_vertex_program
GL_ARB_vertex_shader
GL_ARB_window_pos
GL_ARB_draw_buffers
GL_ATI_draw_buffers
GL_ATI_element_array
GL_ATI_envmap_bumpmap
GL_ATI_fragment_shader
GL_ATI_map_object_buffer
GL_ATI_separate_stencil
GL_ATI_texture_env_combine3
GL_ATI_texture_float
GL_ATI_texture_mirror_once
GL_ATI_vertex_array_object
GL_ATI_vertex_attrib_array_object
GL_ATI_vertex_streams
GL_ATIX_texture_env_combine3
GL_ATIX_texture_env_route
GL_ATIX_vertex_shader_output_point_size
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_blend_color
GL_EXT_blend_func_separate
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_clip_volume_hint
GL_EXT_draw_range_elements
GL_EXT_fog_coord
GL_EXT_framebuffer_object
GL_EXT_multi_draw_arrays
GL_EXT_packed_pixels
GL_EXT_point_parameters
GL_EXT_rescale_normal
GL_EXT_secondary_color
GL_EXT_separate_specular_color
GL_EXT_shadow_funcs
GL_EXT_stencil_wrap
GL_EXT_texgen_reflection
GL_EXT_texture3D
GL_EXT_texture_compression_s3tc
GL_EXT_texture_cube_map
GL_EXT_texture_edge_clamp
GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3
GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod_bias
GL_EXT_texture_mirror_clamp
GL_EXT_texture_object
GL_EXT_texture_rectangle
GL_EXT_vertex_array
GL_EXT_vertex_shader
GL_HP_occlusion_test
GL_NV_blend_square
GL_NV_occlusion_query
GL_NV_texgen_reflection
GL_SGI_color_matrix
GL_SGIS_generate_mipmap
GL_SGIS_multitexture
GL_SGIS_texture_border_clamp
GL_SGIS_texture_edge_clamp
GL_SGIS_texture_lod
GL_SUN_multi_draw_arrays
GL_WIN_swap_hint
WGL_EXT_extensions_string
WGL_EXT_swap_control


[Kolano]

I have big problems with both 1.4.0pre10 and 1.4.0. After I add my extras directory to the celestia config file, both those versions crash. The second 1.4.0pre9-F release exe in the same dir using the same config loads without issue.

It will take me a while to determine if its a specific add-on that causees the issue. If anyone can provide guideance as to what changed between those releases so I can narrow my focus it would be apprieciated.

[Dirl]

I have a problem with script commands "Modify", "Beginning" and "Ending". This commands doesn't work. But in Celestia v1.3.2 it works.

(Win2000, Celestia v1.4.0.)

P.S. Exuse my English.

[selden]

Exactly what problems do you see?

They work fine for me.

[Vincent]

1. When you change the Timerate from a script command, Celestia still displays <Real Time> on the top right hand corner, whereas it displays the right Timerate when you change it from the <J>/<L> keys.

2. When you change the Timerate from a script command, and then pause the script, and resume it, Celestia resets the Timerate to <Realtime> whereas it should keep the previous value set by the script command.

Here's a script you can use as an example to show this bug:

Code: Select all

{
timerate { rate 1 }
print { origin "bottomleft"  row -5  column 3  duration 8 text "Timerate set to [Real time]." }
wait { duration 8 }

timerate { rate 1e4 }
print { origin "bottomleft"  row -5  column 3  duration 8 text "Timerate set to [10000x faster].\nCelestia still displays <Real time>." }
wait { duration 8 }

print { origin "bottomleft"  row -5  column 3  duration 8 text "Press the Space bar twice to pause and resume the script...." }
wait { duration 8 }
wait { duration 4 }

print { origin "bottomleft"  row -5  column 3  duration 8 text "Timerate has been reset to [Real Time] whereas\nit should have remained on [10000x faster]." }
wait { duration 8 }
}

[fsgregs]

I can confirm the time rate display problem. It occurs with cel:urls also. Click on a cel:url that has been set to a faster time (e.g. - 100x faster), and Celestia will go to that location and set itself at 100x faster. So far, so good. Then, change the time to real time using the keyboard [\] command. The time display will correctly display real time.

Now, click the cel:url again. Celestia will again speed up to 100x faster, but the time display will continue to display real time, or whatever time you last set it at with the keyboard. In other words, Celestia is not changing the display to match the true speed, when reacting to script commands or cel:url's.

This is a serious problem for me, since I use cel:urls a lot in my educational work. It will confuse a lot of people, who will not know what time rate they are actually on.



Frank

[sch]

I install celestia 1.4.0 final in Linux with autopackage
Debian 3.0, nVIDIA FX 5600/128Mb
Problems:
1) Lost many planet and moon labels (Jupiter, Saturn, Io, Titan and many other).
Earth, Venera, Sun labels is present;
2) Not worked VT levels 11 and 12 (in Windows 1.4.0 final worked);
3) Milky Way and M31not show.

[danielj]

I can confirm it.I can??t change the month.I try to see the Deep Impact colision and couldn??t see it.I am using Windows XP SP2 with the latest Microsoft corrections and the WMF disabled.

Chris:

I have discovered that the date display cannot be changed in 1.4.0 final when trying to use the numeric keyboard (with num lock on). I now realize that since you mapped that keyboard to move the screen view in Celestia, it may not be usable for entering dates or numbers in Celestia.

I can change the date when using the numbers at the top of the main keyboard. I was able to change all dates and times.

Sorry for any confusion

Frank

How did you change the month 'Dec'??

Bye Fridger

[Harry]

1. When you change the Timerate from a script command, Celestia still displays <Real Time> on the top right hand corner, whereas it displays the right Timerate when you change it from the <J>/<L> keys.

The bug apparently was fixed for CEL-Urls some time ago by Chris, so these should already work correctly in 1.4.1. For scripts, I just checked in a fix into CVS.

Harald