Triple like_ship crash?!?

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
Lestradae
---- E L I T E ----
---- E L I T E ----
Posts: 3095
Joined: Tue Apr 17, 2007 10:30 pm
Location: Vienna, Austria

Triple like_ship crash?!?

Post by Lestradae »

Perhaps someone can make something of my error log.

For a week now, I have strange slowdowns and de-facto crashes (the game freezes completely) with my new oxp I'm working on.

I have gone through everything x times, but don't find what's wrong. I use the new options of is_template and like_ship masively, with like_ship triple relations. But, according to the devs, that should not be a problem.

I can't seem to find anything in my error log, though. This log was taken after a sloooowdown -> freeze with only my oxp and all dependant oxps in:
[log.header]: Opening log for Oolite version 1.72.1 (x86-32 test release) under Windows at 2009-01-10 11:57:18 +0100.
2 processors detected.
Note that the contents of the log file can be adjusted by editing logcontrol.plist.

[joystickHandler.init]: Number of joysticks detected: 0
[display.mode.list.native]: Windows native resolution detected: 1280 x 800
[rendering.opengl.version]: OpenGL renderer version: 2.1.1 ("2.1.1")
Vendor: NVIDIA Corporation
Renderer: GeForce 8600M GT/PCI/SSE2
[rendering.opengl.extensions]: OpenGL extensions (144):
GL_ARB_color_buffer_float GL_ARB_depth_texture GL_ARB_draw_buffers 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_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two 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_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_bindable_uniform GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels 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_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc 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_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent 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_buffer_float 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_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 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_parameter_buffer_object 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_transform_feedback 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_NV_vertex_program3 GL_NVX_conditional_render GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
[searchPaths.dumpAll]: ---> OXP search paths:
(oolite.app/Resources, AddOns, "AddOns/Drones 1.01.oxp", AddOns/MaegilsMissiles.oxp, AddOns/milmissile.oxp, "AddOns/Missiles and Bombs v1.2.oxp", AddOns/nuke.oxp, AddOns/thargmissile.oxp, "AddOns/Zzzz Oolite Shipyards Extension Beta312NEXT.oxp", "AddOns/Zzzz OSE INRA Ultracarrier.oxp", "AddOns/Zzzzz OSE Upgrade-12NEXT.oxp")
[dataCache.rebuild.explicitFlush]: Cache explicitly flushed with shift key. Rebuilding from scratch.
[shipData.load.begin]: Loading ship data...
[shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved:
[script.load.world.listAll]: Loaded 22 world scripts: "chaff_exhausted", "chaff_refill", "chaff_set", "chaff_set_variation", "clipperschedule", "dredger_appearance", "ExecutiveFlightSchedule", "frog_show", "INRAPatrols1", "INRAPatrols2", "missionaries", "NavyPatrols1", "NavyPatrols2", "oolite-cloaking-device" 1.72.1, "oolite-constrictor-hunt" 1.72.1, "oolite-nova" 1.72.1, "oolite-thargoid-plans" 1.72.1, "oolite-trumbles" 1.72.1, "SalezaPatrol", "SIRFYardStations1", "SIRFYardStations2", "supercobra_placement"
[plist.parse.foundation.failed]: Failed to parse AddOns/Missiles and Bombs v1.2.oxp/AIs/missileAI.plist as a property list using Foundation. Retrying using homebrew parser. WARNING: the homebrew parser is deprecated and will be removed in a future version of Oolite.
Parse failed at line 2 (char 25) - extra data after parsed string
[plist.homebrew.parseError]: Property list isn't in XML format, homebrew parser can't help you.
[dataCache.willWrite]: About to write data cache.
[dataCache.write.success]: Wrote data cache.
Can someone see something potentially useful in there? I can't.

:?

L

Addendum: It say in the logcontrol.plist that I can get more info out of the log:
Log output can be modified using the following preference keys:
logging-show-app-name
logging-show-class
logging-show-function
logging-show-file-and-line
logging-echo-to-stderr
Erm ... and how, exactly, do I do that? :oops:
User avatar
Commander McLane
---- E L I T E ----
---- E L I T E ----
Posts: 9520
Joined: Thu Dec 14, 2006 9:08 am
Location: a Hacker Outpost in a moderately remote area
Contact:

Re: Triple like_ship crash?!?

Post by Commander McLane »

Well, the two error messages are very easy to understand. Let's start with the second one:
[plist.parse.foundation.failed]: Failed to parse AddOns/Missiles and Bombs v1.2.oxp/AIs/missileAI.plist as a property list using Foundation. Retrying using homebrew parser. WARNING: the homebrew parser is deprecated and will be removed in a future version of Oolite.
Parse failed at line 2 (char 25) - extra data after parsed string
[plist.homebrew.parseError]: Property list isn't in XML format, homebrew parser can't help you.
It tells you exactly what's wrong: The file 'missileAI.plist', which you find inside the OXP 'Missiles and Bombs v1.2.oxp' is corrupt (has an error in it), and can therefore not be read and used by Oolite. It even tells you in which line of the file to look for the error. What more do you want?

The first one:
[shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved:
It simply tells you that one or more shipdata-entries are linked via like_ship to another entry/entries that doesn't/don't exist.

There a dozens of possible reasons for that. Most likely you have either not all OXPs your OXPs is depending on installed, or you have made a typo/typos in one or more of your like_ship-keys. (For instance, linking via like_ship to an entry 'anconda-player' (instead of 'anaconda-player' would of course not work and produce this error.)
User avatar
JensAyton
Grand Admiral Emeritus
Grand Admiral Emeritus
Posts: 6657
Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:

Post by JensAyton »

If you post the OXP somewhere, one of us godlike beings of light with trunk builds can tell you which shipdata.plist entries have like_ship references that cannot be resolved (that error message has been fixed). I probably can’t do it today, because I’m about to go and do some of that Real Life stuff.
User avatar
Lestradae
---- E L I T E ----
---- E L I T E ----
Posts: 3095
Joined: Tue Apr 17, 2007 10:30 pm
Location: Vienna, Austria

...

Post by Lestradae »

Thanks again, guys.

@Cmdr McLane:

Didn't care that much about the missileAI as this one can't be the culprit, as it works without problems in other configurations. So Ramirez is innocent. I must have done something with the like_ship trees I use. But corrected those errors in Missiles & Bombs now anyways.

I'm surprised that a disfunctional like_ship link leads to such a freeze-over, and wasn't able to find the error by going through the relevant part of the shipdata.plist myself. OK, perhaps that's the problem.

@Ahruman:
Ahruman wrote:
If you post the OXP somewhere, one of us godlike beings of light with trunk builds can tell you which shipdata.plist entries have like_ship references that cannot be resolved (that error message has been fixed). I probably can’t do it today, because I’m about to go and do some of that Real Life stuff.
*looks heavenward*

Thanks for the offer, the oxp - to anyone else, this is a WiP version NOT YET INTENDED OR SUITABLE TO BE USED IN NORMAL PLAY!!! - can be found here:

http://www.box.net/shared/static/433cozr1kv.zip

The like_ship error must be somewhere in shipdata.plist, if it is there.

The WiP contains a (hacked test pilot) savegame with an Overtuned Juggernaut. The freeze problem can be observed with any ship, though, including the Jameson Cobra Mk III :(

Thanks very much you have a look at it, that's appreciated :)

L
User avatar
JensAyton
Grand Admiral Emeritus
Grand Admiral Emeritus
Posts: 6657
Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:

Post by JensAyton »

The fixed error message is:

Code: Select all

 [shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: interstellar-escortscavengerhermitexplorer, tiger-mk1-navy, tiger-mk1-pirate, tiger-mk1-police
A quick check confirms that these four ships are based on two templates that don’t exist.
User avatar
Lestradae
---- E L I T E ----
---- E L I T E ----
Posts: 3095
Joined: Tue Apr 17, 2007 10:30 pm
Location: Vienna, Austria

...

Post by Lestradae »

Thanks again, Ahruman :D

BTW, that was not the reason for the freeze. A betatester of OSE found it in the meantime ... so I can continue oxp'ing.

Cheers

L
Post Reply