uninstall an OXP

[DaddyHoggy]

Pics seem to be missing from some wiki pages now... I've noticed it with BGS and now SR.

Oh no, it's the SOPA/PIPA black-out!

[maik]

Pics seem to be missing from some wiki pages now... I've noticed it with BGS and now SR.

My mistake, I didn't move the image out of the quick facts box (which does not display them anymore). I corrected both and will do a QA run across the other pages that use the template to catch others where I also forgot to move the image.

Edit: done. There were quite a few, in the majority of cases it seems that I only moved the images when there was e.g. a ship info box to put them in.

[snork]

zarkov, one way to find where you put the Nuit stuff may be to use your OS's search feature, look for files with Nuit-specific names, like e.g. docknuit.dat, then you will should have found the oxp's model folder. One folder upwards should be the Nuit-folder.

[Eric Walch]

zarkov, one way to find where you put the Nuit stuff may be to use your OS's search feature, look for files with Nuit-specific names, like e.g. docknuit.dat, then you will should have found the oxp's model folder. One folder upwards should be the Nuit-folder.

On some systems that proofs to be difficult. On the mac are oxps seen as single files and the content is not indexed for the default search mechanism.

What does work perfect is the terminal and using the 'grep' command.

Code: Select all

$ cd [your AddOn's folder]
$ grep -r -i -l "[search string]" *

That will list all files matching the search string (and hence identifies all the OXPs containing the string).
-r - recursive (Omit to search only current directory)
-i - ignore case (Omit for case-sensitive search)
-l - only show matching files (Omit to show matching lines)
(Thanks Micha for above tips about grep)

First set the search path to your addOns folder. On the mac, just type 'cd' and than drop the addOns folder on the terminal window. (That adds the correct path for you).
Than with grep look for an unique as possible string of which you know it should be in the oxp (like a ships name) and put that between the "".

I think grep works on all platforms. Maybe an idea to put it in the frequently asked questions as more people might look for specific stuff they can't find.

[cim]

zarkov, one way to find where you put the Nuit stuff may be to use your OS's search feature, look for files with Nuit-specific names, like e.g. docknuit.dat, then you will should have found the oxp's model folder. One folder upwards should be the Nuit-folder.

What does work perfect is the terminal and using the 'grep' command.

Code: Select all

$ cd [your AddOn's folder]
$ grep -r -i -l "[search string]" *

That will list all files matching the search string (and hence identifies all the OXPs containing the string).

That will find all files containing the search string inside them. To find all files with a particular name, you'd want

Code: Select all

find [your AddOns folder] -name [filename]

(on Linux, anyway, but I think it works also on Mac command lines)
With OXP structure being what it is, any distinctively-named file in an OXP will of course be mentioned by name within the OXP, so grep works, but find will be significantly faster than grep because it doesn't need to look inside any files. (And also, if one OXP depends on another OXP, find will tell you which OXP contains the file rather than which OXPs depend on that file)

Neither works on Windows, sadly, unless you've installed the software separately, but the standard windows search is good enough for basic work. (Windows XP does have a

Code: Select all

FIND

command, which confusingly is more like grep than find, but isn't very useful as a replacement for grep: stick to the GUI search)

[JensAyton]

On some systems that proofs to be difficult. On the mac are oxps seen as single files and the content is not indexed for the default search mechanism.

That’s not entirely true. File names aren’t (always) indexed, but ship IDs are. However, the preferred AddOns location, in ~/Library/, is excluded by default. To search there, you have to add the search criterion “System files” “are included”.

[snork]

wow, this cross-platforming is really affecting much more than I would have thought.

grep

on my windows XP, only when I install and use un*xutils, or mingw, or some such.

[Eric Walch]

That’s not entirely true. File names aren’t (always) indexed, but ship IDs are.

You are right. Because the standard search never returned a plist file with the content, I thought it didn't find it. But looking better I see it returns the oxp itself as result because its seen as one file. Searching for specific strings inside plists or js scripts shows that they are indexed after all and thus found instantaneously in most cases. Even comments I put in scripts and not only the ship IDs.

Including system files helps of cause, or the oxps in the library they were skipped altogether. I'll remember to include them in a search next time.

[zarkov]

Many thanks to everyone for your time and advice. It was the Nuit station despite it's absence from the log file, but reinstalling system redux and its update has removed it from the screen. The log file looks cleaner (to an extremely inexperienced eye - and I have removed several OXPs), but there remains a consistent failure to connect to the debux console. Would I be right to assume that this could be due to firewall interference and is it important that this connection is established?

Here's the log file....

Code: Select all

14:58:08.046 [log.header]: Opening log for Oolite version 1.76 (x86-32 test release) under Windows at 2012-01-20 14:58:08 +0000.
2 processors detected.
Build options: spoken messages, mass/fuel pricing, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

14:58:08.625 [display.mode.list.native]: Windows native resolution detected: 1024 x 600
14:58:09.031 [joystick.init]: Number of joysticks detected: 0
14:58:09.343 [searchPaths.dumpAll]: Unrestricted mode - resource paths:
    Resources
    ../AddOns
    ../AddOns/Armoury 1.09.oxp
    ../AddOns/Basic-debug.oxp
    ../AddOns/Superhubv1.2.oxp
    ../AddOns/System_Redux.oxp
    ../AddOns/thargoid_wars 4.3.oxp
14:58:09.343 [rendering.opengl.version]: OpenGL renderer version: 1.4.0 ("1.4.0 - Build 7.14.10.4906"). Vendor: "Intel". Renderer: "Intel 945GM".
14:58:09.343 [rendering.opengl.extensions]: OpenGL extensions (49):
GL_ARB_transpose_matrix, GL_EXT_texture_compression_s3tc, GL_ARB_texture_cube_map, GL_ARB_texture_env_dot3, GL_NV_texgen_reflection, GL_EXT_blend_color, GL_EXT_rescale_normal, GL_ARB_texture_env_combine, GL_EXT_separate_specular_color, GL_ARB_texture_border_clamp, GL_EXT_fog_coord, GL_IBM_texture_mirrored_repeat, GL_EXT_draw_range_elements, GL_NV_blend_square, GL_ARB_depth_texture, GL_EXT_texture_env_combine, GL_EXT_multi_draw_arrays, GL_EXT_bgra, GL_ARB_texture_env_add, GL_ARB_shadow, GL_EXT_packed_pixels, GL_EXT_texture3D, GL_EXT_blend_subtract, GL_ARB_window_pos, GL_WIN_swap_hint, GL_EXT_texture_lod_bias, GL_ARB_texture_compression, GL_EXT_secondary_color, GL_ARB_texture_env_crossbar, GL_3DFX_texture_compression_FXT1, GL_EXT_shadow_funcs, GL_EXT_abgr, GL_ARB_fragment_program, GL_SGIS_texture_edge_clamp, GL_SGIS_generate_mipmap, GL_ARB_vertex_program, GL_EXT_texture_env_add, GL_EXT_stencil_two_side, GL_EXT_cull_vertex, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_texture_filter_anisotropic, GL_EXT_clip_volume_hint, GL_ARB_point_parameters, GL_ARB_multitexture, GL_EXT_stencil_wrap, GL_EXT_compiled_vertex_array, GL_ARB_vertex_buffer_object, GL_SGIS_texture_lod
14:58:09.421 [rendering.opengl.gpuSpecific]: Matched GPU configuration "Intel GMA 900/950 family".
14:58:09.421 [rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_language_100 is not available).
14:58:09.437 [speech.synthesis]: Spoken messages are off.
14:58:11.484 [script.load.world.listAll]: Loaded 12 world scripts:
    ams_system 2.02
    armoury_machineScript.js 1.00
    CT_Script 2.0
    oolite-cloaking-device 1.76
    oolite-constrictor-hunt 1.76
    oolite-nova 1.76
    oolite-thargoid-plans 1.76
    oolite-trumbles 1.76
    PAGroove_superhubPopulator 1.1
    System Redux 1.2 1.2
    System Redux 1.2.3
    thargoid_wars
14:58:18.359 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'No connection could be made because the target machine actively refused it.

' (outStream status: 7, inStream status: 7)."
14:58:18.359 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'unknown error.' (outStream status: 0, inStream status: 0)."
14:58:18.359 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
14:58:18.531 [loading.complete]: ========== Loading complete. ==========
14:58:26.625 [script.load.world.listAll]: Loaded 12 world scripts:
    ams_system 2.02
    armoury_machineScript.js 1.00
    CT_Script 2.0
    oolite-cloaking-device 1.76
    oolite-constrictor-hunt 1.76
    oolite-nova 1.76
    oolite-thargoid-plans 1.76
    oolite-trumbles 1.76
    PAGroove_superhubPopulator 1.1
    System Redux 1.2 1.2
    System Redux 1.2.3
    thargoid_wars
15:06:52.187 [gameController.exitApp]: .GNUstepDefaults synchronized.

Closing log at 2012-01-20 15:06:52 +0000.

I've just noticed reference to "oolite-cloaking-device" Is this a handy piece of kit I can access in the heat of battle

[Commander McLane]

I've just noticed reference to "oolite-cloaking-device" Is this a handy piece of kit I can access in the heat of battle

Yes, once you've got it, which you will only in a higher galaxy.

[JensAyton]

…there remains a consistent failure to connect to the debux console. Would I be right to assume that this could be due to firewall interference and is it important that this connection is established?

Not unless you’re trying to use it, although it is a bit odd for a firewall to stop a computer from connecting to itself.

[Thargoid]

I just swapped from Norman AV suite (inc firewall) to M$ Essentials and Windows firewall, and the first time I ran the game afterwards I had to OK the use of the debug console with the firewall.

Remembering that you can have the console on a different machine to the one the game is on, it's perhaps not so odd? It's defined as an inbound rule under the firewall (Win7 Home Premium).

[zarkov]

Thanks again - I wouldn't know what to do with a debug console so I'm happy to leave it well alone.