OoliteStarter question

[AndyEW]

As the Mac port of Oolite is falling behind the Windows version, I decided to try running the Windows version on my Mac using CrossOver and it works really well. Gameplay is good, sound and video are good. The only thing I'm having trouble with is OoliteStarter. I unpacked the files in OoliteStarter-0.1.33-generic.zip to the VM (or Bottle as it's called in CrossOver). Using the Crossover options, I ran the run.cmd but got the error message below. How should OoliteStarter be started?

The command "/Users/andy/Library/Application Support/CrossOver/Bottles/Oolite/drive_c/OoliteStarter-0.1.33/run.cmd" returned 1.

Command error text:
[mvk-info] MoltenVK version 1.2.10, supporting Vulkan version 1.2.290.
The following 111 Vulkan extensions are supported:
VK_KHR_16bit_storage v1
VK_KHR_8bit_storage v1
VK_KHR_bind_memory2 v1
VK_KHR_buffer_device_address v1
VK_KHR_calibrated_timestamps v1
VK_KHR_copy_commands2 v1
VK_KHR_create_renderpass2 v1
VK_KHR_dedicated_allocation v3
VK_KHR_deferred_host_operations v4
VK_KHR_depth_stencil_resolve v1
VK_KHR_descriptor_update_template v1
VK_KHR_device_group v4
VK_KHR_device_group_creation v1
VK_KHR_driver_properties v1
VK_KHR_dynamic_rendering v1
VK_KHR_external_fence v1
VK_KHR_external_fence_capabilities v1
VK_KHR_external_memory v1
VK_KHR_external_memory_capabilities v1
VK_KHR_external_semaphore v1
VK_KHR_external_semaphore_capabilities v1
VK_KHR_fragment_shader_barycentric v1
VK_KHR_format_feature_flags2 v2
VK_KHR_get_memory_requirements2 v1
VK_KHR_get_physical_device_properties2 v2
VK_KHR_get_surface_capabilities2 v1
VK_KHR_imageless_framebuffer v1
VK_KHR_image_format_list v1
VK_KHR_incremental_present v2
VK_KHR_maintenance1 v2
VK_KHR_maintenance2 v1
VK_KHR_maintenance3 v1
VK_KHR_map_memory2 v1
VK_KHR_multiview v1
VK_KHR_portability_subset v1
VK_KHR_push_descriptor v2
VK_KHR_relaxed_block_layout v1
VK_KHR_sampler_mirror_clamp_to_edge v3
VK_KHR_sampler_ycbcr_conversion v14
VK_KHR_separate_depth_stencil_layouts v1
VK_KHR_shader_draw_parameters v1
VK_KHR_shader_float_controls v4
VK_KHR_shader_float16_int8 v1
VK_KHR_shader_integer_dot_product v1
VK_KHR_shader_non_semantic_info v1
VK_KHR_shader_subgroup_extended_types v1
VK_KHR_spirv_1_4 v1
VK_KHR_storage_buffer_storage_class v1
VK_KHR_surface v25
VK_KHR_swapchain v70
VK_KHR_swapchain_mutable_format v1
VK_KHR_synchronization2 v1
VK_KHR_timeline_semaphore v2
VK_KHR_uniform_buffer_standard_layout v1
VK_KHR_variable_pointers v1
VK_KHR_vertex_attribute_divisor v1
VK_EXT_4444_formats v1
VK_EXT_buffer_device_address v2
VK_EXT_calibrated_timestamps v2
VK_EXT_debug_marker v4
VK_EXT_debug_report v10
VK_EXT_debug_utils v2
VK_EXT_descriptor_indexing v2
VK_EXT_extended_dynamic_state v1
VK_EXT_extended_dynamic_state2 v1
VK_EXT_extended_dynamic_state3 v2
VK_EXT_external_memory_host v1
VK_EXT_fragment_shader_interlock v1
VK_EXT_hdr_metadata v3
VK_EXT_headless_surface v1
VK_EXT_host_image_copy v1
VK_EXT_host_query_reset v1
VK_EXT_image_robustness v1
VK_EXT_inline_uniform_block v1
VK_EXT_layer_settings v2
VK_EXT_memory_budget v1
VK_EXT_metal_objects v2
VK_EXT_metal_surface v1
VK_EXT_pipeline_creation_cache_control v3
VK_EXT_pipeline_creation_feedback v1
VK_EXT_post_depth_coverage v1
VK_EXT_private_data v1
VK_EXT_robustness2 v1
VK_EXT_sample_locations v1
VK_EXT_scalar_block_layout v1
VK_EXT_separate_stencil_usage v1
VK_EXT_shader_atomic_float v1
VK_EXT_shader_demote_to_helper_invocation v1
VK_EXT_shader_stencil_export v1
VK_EXT_shader_subgroup_ballot v1
VK_EXT_shader_subgroup_vote v1
VK_EXT_shader_viewport_index_layer v1
VK_EXT_subgroup_size_control v2
VK_EXT_surface_maintenance1 v1
VK_EXT_swapchain_colorspace v5
VK_EXT_swapchain_maintenance1 v1
VK_EXT_texel_buffer_alignment v1
VK_EXT_texture_compression_astc_hdr v1
VK_EXT_vertex_attribute_divisor v3
VK_EXT_transform_feedback v1
VK_AMD_gpu_shader_half_float v2
VK_AMD_negative_viewport_height v1
VK_AMD_shader_image_load_store_lod v1
VK_AMD_shader_trinary_minmax v1
VK_IMG_format_pvrtc v1
VK_INTEL_shader_integer_functions2 v1
VK_GOOGLE_display_timing v1
VK_MVK_macos_surface v3
VK_MVK_moltenvk v37
VK_NV_fragment_shader_barycentric v1
VK_NV_glsl_shader v1
[mvk-info] GPU device:
model: Apple M4 Pro
type: Integrated
vendorID: 0x106b
deviceID: 0x1a0003f1
pipelineCacheUUID: 950A7B52-1A00-03F1-0000-000000000000
GPU memory available: 53084 MB
GPU memory used: 0 MB
Metal Shading Language 3.2
supports the following GPU Features:
GPU Family Metal 3
GPU Family Apple 9
GPU Family Apple 8
GPU Family Apple 7
GPU Family Apple 6
GPU Family Apple 5
GPU Family Apple 4
GPU Family Apple 3
GPU Family Apple 2
GPU Family Apple 1
GPU Family Mac 2
GPU Family Mac 1
GPU Family Common 3
GPU Family Common 2
GPU Family Common 1
macOS GPU Family 2 v1
macOS GPU Family 1 v4
macOS GPU Family 1 v3
macOS GPU Family 1 v2
macOS GPU Family 1 v1
[mvk-info] Created VkInstance for Vulkan version 1.0.0, as requested by app, with the following 2 Vulkan extensions enabled:
VK_KHR_external_memory_capabilities v1
VK_KHR_get_physical_device_properties2 v2
[mvk-info] MoltenVK version 1.2.10, supporting Vulkan version 1.2.290.
The following 111 Vulkan extensions are supported:
VK_KHR_16bit_storage v1
VK_KHR_8bit_storage v1
VK_KHR_bind_memory2 v1
VK_KHR_buffer_device_address v1
VK_KHR_calibrated_timestamps v1
VK_KHR_copy_commands2 v1
VK_KHR_create_renderpass2 v1
VK_KHR_dedicated_allocation v3
VK_KHR_deferred_host_operations v4
VK_KHR_depth_stencil_resolve v1
VK_KHR_descriptor_update_template v1
VK_KHR_device_group v4
VK_KHR_device_group_creation v1
VK_KHR_driver_properties v1
VK_KHR_dynamic_rendering v1
VK_KHR_external_fence v1
VK_KHR_external_fence_capabilities v1
VK_KHR_external_memory v1
VK_KHR_external_memory_capabilities v1
VK_KHR_external_semaphore v1
VK_KHR_external_semaphore_capabilities v1
VK_KHR_fragment_shader_barycentric v1
VK_KHR_format_feature_flags2 v2
VK_KHR_get_memory_requirements2 v1
VK_KHR_get_physical_device_properties2 v2
VK_KHR_get_surface_capabilities2 v1
VK_KHR_imageless_framebuffer v1
VK_KHR_image_format_list v1
VK_KHR_incremental_present v2
VK_KHR_maintenance1 v2
VK_KHR_maintenance2 v1
VK_KHR_maintenance3 v1
VK_KHR_map_memory2 v1
VK_KHR_multiview v1
VK_KHR_portability_subset v1
VK_KHR_push_descriptor v2
VK_KHR_relaxed_block_layout v1
VK_KHR_sampler_mirror_clamp_to_edge v3
VK_KHR_sampler_ycbcr_conversion v14
VK_KHR_separate_depth_stencil_layouts v1
VK_KHR_shader_draw_parameters v1
VK_KHR_shader_float_controls v4
VK_KHR_shader_float16_int8 v1
VK_KHR_shader_integer_dot_product v1
VK_KHR_shader_non_semantic_info v1
VK_KHR_shader_subgroup_extended_types v1
VK_KHR_spirv_1_4 v1
VK_KHR_storage_buffer_storage_class v1
VK_KHR_surface v25
VK_KHR_swapchain v70
VK_KHR_swapchain_mutable_format v1
VK_KHR_synchronization2 v1
VK_KHR_timeline_semaphore v2
VK_KHR_uniform_buffer_standard_layout v1
VK_KHR_variable_pointers v1
VK_KHR_vertex_attribute_divisor v1
VK_EXT_4444_formats v1
VK_EXT_buffer_device_address v2
VK_EXT_calibrated_timestamps v2
VK_EXT_debug_marker v4
VK_EXT_debug_report v10
VK_EXT_debug_utils v2
VK_EXT_descriptor_indexing v2
VK_EXT_extended_dynamic_state v1
VK_EXT_extended_dynamic_state2 v1
VK_EXT_extended_dynamic_state3 v2
VK_EXT_external_memory_host v1
VK_EXT_fragment_shader_interlock v1
VK_EXT_hdr_metadata v3
VK_EXT_headless_surface v1
VK_EXT_host_image_copy v1
VK_EXT_host_query_reset v1
VK_EXT_image_robustness v1
VK_EXT_inline_uniform_block v1
VK_EXT_layer_settings v2
VK_EXT_memory_budget v1
VK_EXT_metal_objects v2
VK_EXT_metal_surface v1
VK_EXT_pipeline_creation_cache_control v3
VK_EXT_pipeline_creation_feedback v1
VK_EXT_post_depth_coverage v1
VK_EXT_private_data v1
VK_EXT_robustness2 v1
VK_EXT_sample_locations v1
VK_EXT_scalar_block_layout v1
VK_EXT_separate_stencil_usage v1
VK_EXT_shader_atomic_float v1
VK_EXT_shader_demote_to_helper_invocation v1
VK_EXT_shader_stencil_export v1
VK_EXT_shader_subgroup_ballot v1
VK_EXT_shader_subgroup_vote v1
VK_EXT_shader_viewport_index_layer v1
VK_EXT_subgroup_size_control v2
VK_EXT_surface_maintenance1 v1
VK_EXT_swapchain_colorspace v5
VK_EXT_swapchain_maintenance1 v1
VK_EXT_texel_buffer_alignment v1
VK_EXT_texture_compression_astc_hdr v1
VK_EXT_vertex_attribute_divisor v3
VK_EXT_transform_feedback v1
VK_AMD_gpu_shader_half_float v2
VK_AMD_negative_viewport_height v1
VK_AMD_shader_image_load_store_lod v1
VK_AMD_shader_trinary_minmax v1
VK_IMG_format_pvrtc v1
VK_INTEL_shader_integer_functions2 v1
VK_GOOGLE_display_timing v1
VK_MVK_macos_surface v3
VK_MVK_moltenvk v37
VK_NV_fragment_shader_barycentric v1
VK_NV_glsl_shader v1
[mvk-info] GPU device:
model: Apple M4 Pro
type: Integrated
vendorID: 0x106b
deviceID: 0x1a0003f1
pipelineCacheUUID: 950A7B52-1A00-03F1-0000-000000000000
GPU memory available: 53084 MB
GPU memory used: 0 MB
Metal Shading Language 3.2
supports the following GPU Features:
GPU Family Metal 3
GPU Family Apple 9
GPU Family Apple 8
GPU Family Apple 7
GPU Family Apple 6
GPU Family Apple 5
GPU Family Apple 4
GPU Family Apple 3
GPU Family Apple 2
GPU Family Apple 1
GPU Family Mac 2
GPU Family Mac 1
GPU Family Common 3
GPU Family Common 2
GPU Family Common 1
macOS GPU Family 2 v1
macOS GPU Family 1 v4
macOS GPU Family 1 v3
macOS GPU Family 1 v2
macOS GPU Family 1 v1
[mvk-info] Created VkInstance for Vulkan version 1.0.0, as requested by app, with the following 2 Vulkan extensions enabled:
VK_KHR_external_memory_capabilities v1
VK_KHR_get_physical_device_properties2 v2

[hiran]

This is a complex problem.

OoliteStarter is a Java Swing application. It should not require any more than a standard Java 17 or later JVM and a graphical desktop.
I do not have a Mac hence I cannot reproduce your problem. But from your description I read that Java cannot startup for some reason. None of the lines you posted stem from OoliteStarter itself.

Which OS do you have?
Which Java version is installed?
Which version of Crossover did you use?
Which version of Java was loaded through the batch file?
Can you in this way run other java applications?

The problem you describe might be introduced due to Crossover being between Java and the OS. I checked the Crossover compatibility list for Java but the result is sobering.

Maybe someone with Mac/Crossover knowledge can give more insight. Otherwise I'd simply try to run OoliteStarter using the shell script.

[AndyEW]

Hello Hiram and thank you for your reply. In answer to your questions:
macOS Tahoe 26.0 on a M4 Mac mini
Crossover 25.1.1

The Java version is where it get embarrassing for me as I don't think there's a version installed on the bottle (VM). I will install a current standard JVM and see if makes a difference.

If it doesn't then I will just have to deal with the expansions the old fashioned way I will let you know but please don't waste any more time on it.

Cheers,

Andy

[hiran]

I will install a current standard JVM and see if makes a difference.

If it doesn't then I will just have to deal with the expansions the old fashioned way

There is a way inbetween. If you cannot run OoliteStarter within Crossover you can still run it natively on MacOs. It then can manage your expansions even for a crossovered Oolite. I guess the installation will not be autodetected so you might need to configure it manually. But while doing so you can also provide the path to the executable. Try pointing to a shell script that brings up the crossover version of Oolite.

Let me know what worked for you - then I don't have to spend time mulling over it....

[AndyEW]

My technical skills are not what they where
Java v8 won't install on the CrossOver VM
Java v4 should install on the CrossOver VM but won't (the icons are displayed after the install but the software isn't there)

I do have the macOS version of OoliteStarter installed directly on the Mac mini, and that works fine. The folders containing Oolite on the CrossOver VM are visible to macOS, so the question is how do I point OolitStarter at them?

Any hints or tips would be greatly appreciated.

Cheers,

Andy

[hiran]

My technical skills are not what they where
Java v8 won't install on the CrossOver VM
Java v4 should install on the CrossOver VM but won't (the icons are displayed after the install but the software isn't there)

I do have the macOS version of OoliteStarter installed directly on the Mac mini, and that works fine. The folders containing Oolite on the CrossOver VM are visible to macOS, so the question is how do I point OolitStarter at them?

Any hints or tips would be greatly appreciated.

Mind the fact you need Java 17 or higher.

I'd assume Mr Gimlet would push rookies where they need to be. Maybe he is as helpful and annoying as Clippy.

See the documentation:
- https://github.com/OoliteProject/Oolite ... tallations
- https://github.com/OoliteProject/Oolite ... e-versions

Hmm, once it is called 'installation', once it is 'version'. Will look into that. And feel free to raise questions - I can likely improve the text as well.