Just upgraded to 1.70

[ArkanoiD]

What happened to starfield and planet textures? Sky clouds are incredibly ugly now..

[LittleBear]

Had the same problem with square stars and nebulas all messed up. Took out all OXPs and no problem. I suspect somthing is rotten in the states of an OXP somwhere. Putting OXPs back in one at a time. Let you know if I find the culprit.

[JensAyton]

The sky shouldn’t look any different. Planet textures are (still) disabled due to crashiness.

[another_commander]

What happened to starfield and planet textures? Sky clouds are incredibly ugly now..

Can you please post a screenshot and your system specs? I cannot see anything wrong here.

[Frame]

Had the same problem with square stars and nebulas all messed up. Took out all OXPs and no problem. I suspect somthing is rotten in the states of an OXP somwhere. Putting OXPs back in one at a time. Let you know if I find the culprit.

yes yes blame it on us...

[ArkanoiD]

Thats's how star clouds used to look in 1.67:



and now in 1.70 they look like this



And for the planets, it just looks that a feature called "procedural textures" is gone, planets have the same boring look early elite versions had

[another_commander]

I'd still like to know your system specs. Also, try LittleBear's suggestion and run without any OXPs installed. First 50 and last 50 lines of your stderr.txt log would be desirable. Are you running Mac or Windows?
Sorry for the storm of requests, but if this is to be tackled, we will need information.

BTW, don't look for procedural textures, they are out at the moment due to instability reasons.

Are there any other users with this symptom?

[ArkanoiD]

I'd still like to know your system specs. Also, try LittleBear's suggestion and run without any OXPs installed. First 50 and last 50 lines of your stderr.txt log would be desirable. Are you running Mac or Windows?
Sorry for the storm of requests, but if this is to be tackled, we will need information.

BTW, don't look for procedural textures, they are out at the moment due to instability reasons.

Are there any other users with this symptom?

I tried resetting to "strict" mode, it does effectively disable OXPs as well, right? Still the same look I am running RHEL5 (mostly similar to FC6), 3GHz p4 with HT enabled, 512Mb RAM (i feel it is not enough for big space battles, going to upgrade), NVIDIA GoFX5200 with 32Mb VRAM (it is one of those ugly 4kg monsters mistakingly called "notebooks").

2007-12-04 15:48:17.529 oolite[6364] [rendering.opengl.extensions]: OpenGL extensions (112):
GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_half_float_pixel GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow GL_ARB_shader_objects GL_ARB_shading_language_100 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_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_S3_s3tc GL_EXT_texture_env_add 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_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_gpu_program_parameters GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_paletted_texture GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_shared_texture_palette GL_EXT_stencil_two_side GL_EXT_stencil_wrap 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 GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_texture_sRGB GL_EXT_timer_query GL_EXT_vertex_array GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_blend_square GL_NV_copy_depth_to_color GL_NV_depth_clamp GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_framebuffer_multisample_coverage GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_texgen_reflection GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum

[another_commander]

If you are running Linux, I cannot really offer anything more than an educated guess, since I can not perform testing on said platform. In case no other Linux users report similar behavior, my guess would be that the problem could be driver-related. If at all possible, try to test on a different machine. And just to be sure, try renaming the AddOns folder (effectively deleting all OXPs as far as the game is concerned) and see if it changes anything - remember to rename back to AddOns afterwards, of course.

And one more thing. Looking at the nightly build results, I see plenty of implicit function declaration warnings for several OGL extension functions. I don't really like these warnings and I don't get them in Windows. There might be something funny going on there.

[Frame]

i think Ahruman was optimizing the clouds in 1.69, could you try 1.69.1 or 1.69 first an tell if it is the same result ?

btw im running a FX5200 LV128... wiht 128 mb of ram...

also have you set shaders to simple or full.. you can do that in the game options within the game

[ArkanoiD]

i think Ahruman was optimizing the clouds in 1.69, could you try 1.69.1 or 1.69 first an tell if it is the same result ?

btw im running a FX5200 LV128... wiht 128 mb of ram...

also have you set shaders to simple or full.. you can do that in the game options within the game

Could not find Linux binaries for 1.69, where are those?

[LittleBear]

@ArkanoiD.

Thats exactly how it looks on my system with all the OXPs in (windows XP). ATM I'm just playing with about 10 in and its running fine. It is therefore somthing to do with an OXP (quite possibly one of mine ). I'll do the old add another OXP, run, check its OK, add another one to locate the offender.

[Griff]

Just posting that the sky looks fine on my system
windows XP
Graphics card: Nvidia GForce8800GTS - Driver version 169.09 (the beta ones)
No OXP's installed

[Commander McLane]

Sky looks fine on my system. Actually I see no difference to 1.69.1.1, so I guess new galaxy- and nebula-textures are not yet implemented?

MacBook Pro, OS X 10.4.11, ATI Radeon X1600 with 128MB (although my System Profiler for no apparent reason insists on calling it ATY instead of ATI).

By the way: Do all the new planetinfo.plist-keys for clouds etc. (which I supposed to be in the progress-thread, but they aren't, so I don't find them now) work? (Was not mentioned in the release notes, or was it?)

[JensAyton]

Sky looks fine on my system. Actually I see no difference to 1.69.1.1, so I guess new galaxy- and nebula-textures are not yet implemented?

That is correct.

By the way: Do all the new planetinfo.plist-keys for clouds etc. (which I supposed to be in the progress-thread, but they aren't, so I don't find them now) work? (Was not mentioned in the release notes, or was it?)

They should do.