Understanding why?

Rustybolts · Post by **Rustybolts** » Wed Jun 17, 2009 6:16 am

Ive made a new ship (st.oxp posted earlier) but since ive updated the model it fails to work. All ship names related to this were altered in the plists. I fail to see what the error is, anyway here is my latest log file. I am hoping one of you kind peeps can tell me where i need to be looking.

[log.header]: Opening log for Oolite version 1.72.2 (x86-32 test release) under Windows at 2009-06-17 07:06:31 +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: 1024 x 600
[rendering.opengl.version]: OpenGL renderer version: 1.4.0 ("1.4.0 - Build 7.14.10.4926")
Vendor: Intel
Renderer: Intel 945GM
[rendering.opengl.extensions]: OpenGL extensions (50):
GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_multitexture GL_ARB_point_parameters GL_ARB_shadow 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_env_crossbar GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_window_pos 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_compiled_vertex_array GL_EXT_cull_vertex GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_packed_pixels 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_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_lod_bias GL_EXT_texture_filter_anisotropic GL_EXT_texture3D GL_3DFX_texture_compression_FXT1 GL_IBM_texture_mirrored_repeat GL_NV_blend_square GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_WIN_swap_hint
[rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_language_100 is not available).
[searchPaths.dumpAll]: ---> OXP search paths:
(oolite.app/Resources, AddOns, AddOns/wolfwoods_variants.oxp, "AddOns/x-ships.oxp", AddOns/cobra35.oxp, "AddOns/cobraClipper 1.1.oxp", AddOns/FighterHud.oxp, AddOns/oldships.oxp, "AddOns/PlanetFall 1.12.oxp", "AddOns/PlanetFall Link - hOopy Casino 1.0.oxp", AddOns/RandomHits275.oxp, "AddOns/UPS-courier v1.5.4.oxp", AddOns/Ste.oxp, AddOns/Debug.oxp)
[dataCache.rebuild.explicitFlush]: Cache explicitly flushed with shift key. Rebuilding from scratch.
[shipData.load.begin]: Loading ship data...
[plist.parse.foundation.failed]: Failed to parse AddOns/Ste.oxp/Config/shipdata.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 1 (char 1) - extra data after parsed string
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (smooth) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <true/>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (thrust) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <real>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (weapon_position_aft) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (weapon_position_forward) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (weapon_position_port) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (weapon_position_starboard) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (view_position_aft) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (view_position_forward) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (view_position_port) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseWarning]: ----- Bad property list: <key> element (view_position_starboard) found when expecting a value, treating as <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: odd number of elements in <dict>, ignoring trailing <string>.
[plist.homebrew.parseWarning]: ----- Bad property list: expected <key>, got <string>. Allowing for backwards compatibility, but the property list will not function as intended.
[plist.homebrew.parseError]: ***** Property list parser error: invalid token structure.
[shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: ("ups-fuelship2", "ups-fuelship4")
[plist.parse.foundation.failed]: Failed to parse AddOns/Ste.oxp/Config/shipyard.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 1 (char 1) - extra data after parsed string
[plist.homebrew.success]: Successfully interpreted property list... for now.
[script.load.world.listAll]: Loaded 13 world scripts: "clipperschedule" 1.1, "oolite-cloaking-device" 1.72.2, "oolite-constrictor-hunt" 1.72.2, "oolite-nova" 1.72.2, "oolite-thargoid-plans" 1.72.2, "oolite-trumbles" 1.72.2, "PlanetFall" 1.1.2, "Random_Hits", "ups_container" 1.5.3, "ups_docs" 1.5.3, "ups_parcel" 1.5.3, "ups_slaves" 1.5.3, "ups_sun" 1.5.3
[debugTCP.disconnect]: Debug console disconnected with message Lost connection to remote debug console. Stream status: 7. Stream error: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.

[debugTCP.connect.failed]: Failed to connect to debug console at 127.0.0.1:8563.
[dataCache.willWrite]: About to write data cache.
[dataCache.write.success]: Wrote data cache.
[gameController.exitApp]: .GNUstepDefaults synchronized.

Closing log at 2009-06-17 07:07:19 +0100.

Lestradae · Post by **Lestradae** » Wed Jun 17, 2009 6:34 am

OK ...

"weapon_position_port", "weapon_position_starboard" don't work (yet) - perhaps this might be implemented at some point, but atm you can take that out. Shouldn't break anything though.

The rest - seems as if you did open "dict" sometimes without re-closing it "/dict", and that you put "key" entries where "string" should have been.

Perhaps it would help if you published your whole shipdata.plist here. I have different versions from you from the st and ste oxps, but they all differ from each other ... better to have one specific shipdata.plist to concentrate on and get to work!

L

Post by **another_commander** » Wed Jun 17, 2009 6:56 am

Lestradae wrote:
"weapon_position_port", "weapon_position_starboard" don't work (yet) - perhaps this might be implemented at some point, but atm you can take that out.

Leave it in. It will be working in 1.73.

Wiki pages · Post by **Thargoid** » Wed Jun 17, 2009 7:49 am

Specifically I would look in the shipdata.plist at the key immediately before the smooth one. It looks like the value for that key is either missing or malformed, and it's screwing up the rest of the list interpretation.

But as Lestradae says, if you can post up the shipdata.plist (between code tags) then it should be easier to diagnose.

Svengali · Post by **Svengali** » Wed Jun 17, 2009 11:23 am

Another interesting question is why is the search-path list not in alphabetical order? Is it depending on the systems settings?

Lestradae · Post by **Lestradae** » Wed Jun 17, 2009 11:51 am

another_commander wrote:
Lestradae wrote:
"weapon_position_port", "weapon_position_starboard" don't work (yet) - perhaps this might be implemented at some point, but atm you can take that out.
Leave it in. It will be working in 1.73.

That's quite relevant information

Is this already doable with the present trunk revision?

Very good idea imo!

Cheers

L

Post by **another_commander** » Wed Jun 17, 2009 11:53 am

Yes, current trunk has it implemented.

Rustybolts · Post by **Rustybolts** » Wed Jun 17, 2009 3:54 pm

[log.header]: Opening log for Oolite version 1.72.2 (x86-32 test release) under Windows at 2009-06-17 16:41:31 +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: 1024 x 600
[rendering.opengl.version]: OpenGL renderer version: 1.4.0 ("1.4.0 - Build 7.14.10.4926")
Vendor: Intel
Renderer: Intel 945GM
[rendering.opengl.extensions]: OpenGL extensions (50):
GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_multitexture GL_ARB_point_parameters GL_ARB_shadow 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_env_crossbar GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_window_pos 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_compiled_vertex_array GL_EXT_cull_vertex GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_packed_pixels 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_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_lod_bias GL_EXT_texture_filter_anisotropic GL_EXT_texture3D GL_3DFX_texture_compression_FXT1 GL_IBM_texture_mirrored_repeat GL_NV_blend_square GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_WIN_swap_hint
[rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_language_100 is not available).
[searchPaths.dumpAll]: ---> OXP search paths:
(oolite.app/Resources, AddOns, AddOns/wolfwoods_variants.oxp, "AddOns/x-ships.oxp", AddOns/cobra35.oxp, "AddOns/cobraClipper 1.1.oxp", AddOns/FighterHud.oxp, AddOns/oldships.oxp, "AddOns/PlanetFall 1.12.oxp", "AddOns/PlanetFall Link - hOopy Casino 1.0.oxp", AddOns/RandomHits275.oxp, "AddOns/UPS-courier v1.5.4.oxp", AddOns/Debug.oxp, AddOns/Ste.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: ("ups-fuelship2", "ups-fuelship4")
[script.load.world.listAll]: Loaded 13 world scripts: "clipperschedule" 1.1, "oolite-cloaking-device" 1.72.2, "oolite-constrictor-hunt" 1.72.2, "oolite-nova" 1.72.2, "oolite-thargoid-plans" 1.72.2, "oolite-trumbles" 1.72.2, "PlanetFall" 1.1.2, "Random_Hits", "ups_container" 1.5.3, "ups_docs" 1.5.3, "ups_parcel" 1.5.3, "ups_slaves" 1.5.3, "ups_sun" 1.5.3
[debugTCP.disconnect]: Debug console disconnected with message Lost connection to remote debug console. Stream status: 7. Stream error: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.

[debugTCP.connect.failed]: Failed to connect to debug console at 127.0.0.1:8563.
[dataCache.willWrite]: About to write data cache.
[dataCache.write.success]: Wrote data cache.
[gameController.exitApp]: .GNUstepDefaults synchronized.

Closing log at 2009-06-17 16:41:55 +0100.

Above log is after i use my original plist do i take it that there are errors with other peoples oxps and mine loaded fine?

And heres my previous plist

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ste</key>
	<dict>
		<key>aft_eject_position</key>
		<string>0.0 -4.5 -10.5</string>
		<key>ai_type</key>
		<string>traderAI.plist</string>
		<key>cargo_type</key>
		<string>CARGO_NOT_CARGO</string>
		<key>energy_recharge_rate</key>
		<real>4</real>
		<key>exhaust</key>

		<array>
			<string>0.0 -0.9 -14.5 8.0 6.0 8.0</string>
<string>0.0 -0.9 -14.5 8.0 6.0 8.0</string>
		</array>
		<key>forward_weapon_type</key>
		<string>WEAPON_BEAM_LASER</string>
		<key>has_ecm</key>
		<real>0.85</real>
		<key>has_shield_booster</key>
		<real>0.15</real>
		<key>has_shield_enhancer</key>
		<real>0.05</real>
		<key>likely_cargo</key>
		<integer>10</integer>
		<key>max_cargo</key>
		<integer>40</integer>
		<key>max_energy</key>
		<real>300</real>
		<key>max_flight_pitch</key>
		<real>0.8</real>
		<key>max_flight_roll</key>
		<real>1.8</real>
		<key>max_flight_speed</key>
		<real>390</real>
		<key>max_missiles</key>
		<integer>3</integer>
		<key>missile_launch_position</key>
		<string>0.0 -1.75 15.5</string>
		<key>missiles</key>
		<integer>2</integer>
		<key>model</key>
		<string>ste.dat</string>
		<key>name</key>
		<string>Ste</string>
		<key>roles</key>
		<string>trader hunter pirate ste</string>
		<key>thrust</key>
		<real>40</real>
		<key>weapon_position_aft</key>
		<string>0.0 -4.0 -15.0</string>
		<key>weapon_position_forward</key>
		<string>0.0 0.0 15.0</string>
		<key>weapon_position_port</key>
		<string>-21.6 -2.0 -2.0</string>
		<key>weapon_position_starboard</key>
		<string>21.6 -2.0 -2.0</string>
	</dict>
	<key>ste-player</key>
	<dict>
		<key>aft_eject_position</key>
		<string>0.0 -4.5 -10.5</string>
		<key>cargo_type</key>
		<string>CARGO_NOT_CARGO</string>
		<key>energy_recharge_rate</key>
		<real>4</real>
		<key>exhaust</key>
		<array>
			<string>0.0 -0.9 -14.5 8.0 6.0 8.0</string>
<string>0.0 -0.9 -14.5 8.0 6.0 8.0</string>
		</array>
		<key>forward_weapon_type</key>
		<string>WEAPON_BEAM_LASER</string>
		<key>max_cargo</key>
		<integer>40</integer>
		<key>max_energy</key>
		<real>300</real>
		<key>max_flight_pitch</key>
		<real>0.8</real>
		<key>max_flight_roll</key>
		<real>1.8</real>
		<key>max_flight_speed</key>
		<real>390</real>
		<key>max_missiles</key>
		<integer>3</integer>
		<key>missile_launch_position</key>
		<string>0.0 -1.75 15.5</string>
		<key>missiles</key>
		<integer>3</integer>
		<key>model</key>
		<string>ste.dat</string>
		<key>name</key>
		<string>ste</string>
		<key>roles</key>
		<string>player</string>
		<key>thrust</key>
		<real>40</real>
		<key>view_position_aft</key>
		<string>0.0 2.0 -15.0 </string>
		<key>view_position_forward</key>
		<string>0.0 1.4 11.0</string>
		<key>view_position_port</key>
		<string>-9.9 1.5 0.0</string>
		<key>view_position_starboard</key>
		<string>9.9 1.5 10.0</string>
	</dict>
</dict>
</plist>

Rustybolts · Post by **Rustybolts** » Wed Jun 17, 2009 4:00 pm

Thargoid wrote:
Specifically I would look in the shipdata.plist at the key immediately before the smooth one. It looks like the value for that key is either missing or malformed, and it's screwing up the rest of the list interpretation.

But as Lestradae says, if you can post up the shipdata.plist (between code tags) then it should be easier to diagnose.

That plist did have missing values for the key, it was a rehashed version of someone else's plist as an ongoing attempt to get my model working.

Screet · Post by **Screet** » Wed Jun 17, 2009 4:03 pm

I'm not the plist wizard to instantly see the problem. However, there's a feature which might make things a bit easier for you:

Code: Select all

      <key>like_ship</key>
      <string>shipname</string>

This especially does help with player and NPC versions for ships. You will then only have to write the common values once, as the other version can use like_ship to reference these. Should you change one value which both use, both ships will be updated to the new value. That helps to keep consistency where both versions should have the same stats / exhaust positions and such.

Screet

Rustybolts · Post by **Rustybolts** » Wed Jun 17, 2009 5:39 pm

Update : Ste now appears on demo of models at start of game. Not seen it flying yet (which is fair enough!) .But i havnt seen it in shipyards either despite it having 0.99 chance of appearance, heres my shipyard list

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ste-player</key>
	<dict>
		<key>chance</key>
		<real>0.99</real>
		<key>optional_equipment</key>
		<array>
            <string>EQ_CARGO_BAY</string>
			<string>EQ_ECM</string>
			<string>EQ_FUEL_SCOOPS</string>
			<string>EQ_ESCAPE_POD</string>
			<string>EQ_ENERGY_BOMB</string>
			<string>EQ_ENERGY_UNIT</string>
			<string>EQ_NAVAL_ENERGY_UNIT</string>
			<string>EQ_PASSENGER_BERTH</string>
			<string>EQ_WEAPON_PULSE_LASER</string>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<string>EQ_WEAPON_MINING_LASER</string>
			<string>EQ_WEAPON_MILITARY_LASER</string>
			<string>EQ_FUEL_INJECTION</string>
			<string>EQ_SCANNER_SHOW_MISSILE_TARGET</string>
			<string>EQ_MULTI_TARGET</string>
			<string>EQ_GAL_DRIVE</string>
			<string>EQ_SHIELD_BOOSTER</string>
			<string>EQ_NAVAL_SHIELD_BOOSTER</string>
		</array>
		<key>price</key>
		<integer>185000</integer>
		<key>standard_equipment</key>
		<dict>
			<key>extras</key>
			<array>
				<string>EQ_DOCK_COMP</string>
				<string>EQ_ADVANCED_COMPASS</string>
			</array>
			<key>forward_weapon_type</key>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<key>missiles</key>
			<integer>3</integer>
		</dict>
		<key>techlevel</key>
		<integer>3</integer>
	</dict>
</dict>
</plist>

Wiki pages · Post by **Thargoid** » Wed Jun 17, 2009 8:22 pm

One side comment, you've got the Planetfall hOopy casino link extension installed but not the hOopy casino OXP itself, which is needed for it to actually work and the casino to appear planet-side.

Rustybolts · Post by **Rustybolts** » Wed Jun 17, 2009 9:15 pm

Thargoid wrote:
One side comment, you've got the Planetfall hOopy casino link extension installed but not the hOopy casino OXP itself, which is needed for it to actually work and the casino to appear planet-side.

Lol k will install relevant oxp at some point.

Oolite Bulletins

Understanding why?

Understanding why?

..

Re: ..

Re: ..