Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 11/19/2025 in all areas

  1. Across the Seas Scenery Editor and Custom Harbour Guide Create a harbour by placing game-library objects, importing your own static FBX models, or combining both. Use `harbour.json` to define the package and its location. Use the in-game **Scenery Editor** to arrange the objects and export the finished harbour. 1. Create a draft In the game directory that contains `Mods`, create a folder under `Mods/Sceneries`. For a standard Windows installation, the path is `Windows/AcrosstheSeas/Mods/Sceneries`. ```text Mods/ Sceneries/ MyFalmouthHarbour/ harbour.json Quay.fbx Textures/ ``` Save the following as UTF-8 in `harbour.json`. The coordinates are an example near Falmouth. Use your own coordinates and a unique ID for your project. If you do not have a `Quay.fbx` yet, remove that entire entry. A library-only draft can also start with `"models": []`. If your installation includes **Falmouth Demo**, you can open it directly to try the controls. 2. Build in the Scenery Editor 1. From the main menu, open **Scenery Editor**. Select a draft from **Editable sceneries** or click its **D** marker on the map. Choose **Edit scenery**. 2. Fly with **WASD**. Hold the **right mouse button** to look around, use **Page Up / Page Down** to change altitude, or hold **Shift** to move faster. **Esc** opens the pause menu and gives access to **Settings**. 3. To add a built-in object, search or browse the **Object library**, then select an entry to see its preview. Choose **Place library object** and click the terrain. Click again to place another copy of the same object, or choose **Cancel placement** to finish. 4. Click an object in the scene or its entry under **Placed objects** to select it. Hold **Ctrl** while clicking to select multiple objects. Use **Focus selected object** to find the current selection. 5. Use **Move** to drag a coloured axis, **Rotate** to drag the yaw ring, or **Scale** to drag the square handle for uniform scaling. You can also enter **X**, **Y**, **Z**, **Yaw**, and **Scale** directly. **Place with mouse** relocates the selection at its current height. **Snap to ground** adjusts the selection vertically to the ground below it. **Snap** enables 0.5 m position increments and 15° rotation increments where applicable. 6. Use **Duplicate and place**, **Undo**, or **Redo** as needed. Enter a group name and press **Enter** to assign a group. Use **Lock / unlock group** to protect it from accidental edits. **Delete selected library objects** removes library objects. To add a new FBX file or remove a custom FBX entry, close the editor and edit `harbour.json`. 7. Check your work with **Day preview** and **Night preview**, then click **Save draft**. Save before returning to the main menu or editing the JSON by hand. The library includes residential, commercial and industrial buildings, plus harbour equipment such as bollards, fenders and a floodlight. The library bollard provides a mooring point. The library floodlight switches on during night hours. 3. Edit `harbour.json` directly | Field | Meaning | | --- | --- | | `schemaVersion` | Set to `1`. | | `id` | Unique package ID. Use up to 80 lowercase ASCII letters, digits, dots, hyphens or underscores. | | `displayName` | Name displayed in the editor. Defaults to the package ID. | | `status` | Use `"draft"` to edit in the Scenery Editor and `"published"` for normal play. Set it explicitly. | | `anchor` | Geographic origin for the package. Use decimal degrees, with negative longitude west of Greenwich. Bounds are ±85° latitude and ±180° longitude. Optional `altitudeMeters` defaults to 0. | | `models` | Up to 256 placements. A published harbour needs at least one. | | `file` or `libraryId` | Use exactly one per model. Use a local FBX filename such as `"Quay.fbx"`, or a known library ID such as `"small-house"`, `"harbour-bollard"`, `"harbour-fender"`, `"harbour-atlantic-fender"` or `"harbour-floodlight"`. For other library objects, place one in the editor, save the draft and copy its generated ID. | | `offsetMeters` | Local `[X, Y, Z]` in metres from the anchor. Positive Z raises the object. Each axis must stay within ±2,000 m. Default is `[0, 0, 0]`. Confirm X and Y orientation in the editor. | | `yawDegrees`, `scale` | Rotation about the vertical axis (−360° to 360°) and uniform scale (0.01–100). Defaults are 0 and 1. | | `group`, `groupLocked` | Optional editor grouping. Group names can be up to 64 characters. The lock is a JSON boolean. | For custom models, use static geometry with a predictable pivot and check the scale against an in-game object. Put each FBX beside `harbour.json`. Keep external textures inside the package, preferably beside the FBX or in `Textures/`. Use simple materials and check that the textures load in the game. Reuse the same filename in multiple model entries to place copies at different positions. The manifest limit is 256 KiB. Unique FBX files in a package may total up to 64 MiB. Imported FBX placements are also subject to a combined limit of 2 million vertices, including repeated FBX placements. Keep meshes well below the limit for smoother loading. Optional custom terrain Add `terrainReplacement` at the top level of `harbour.json` and add your replacement mesh as a regular FBX model in `models`. For example, the following is the value of the `terrainReplacement` field. The rectangle must have west < east and south < north, with a maximum span of 0.25° on each axis. It hides the streamed low-poly terrain inside the rectangle while the harbour is loaded. Keep the rectangle tight around the replacement and check its edges from the water. This is a visual replacement. It does not alter water height, seabed depth or navigation charts. Imported scenery meshes have collision disabled. 4. Publish and install 1. In the editor, choose **Export finished scenery**. The game saves the draft and writes a ZIP under `Saved/SceneryExports`. The export contains a copy of the manifest marked `"published"`, the referenced package FBX files, and supported image files from the package directory. Built-in library assets are referenced by ID. Exports support up to 1,024 asset files and 512 MiB of asset data. Keep the draft as your editable source. 2. Share the ZIP with any required asset credits and include only files you have permission to redistribute. 3. To install, extract the package folder from the ZIP into `Mods/Sceneries`. Check that the extracted folder contains `harbour.json` and the bundled assets. To update a harbour, replace the previous published package with the new one. Multiple published packages with the same ID are skipped. 4. Reopen the voyage selection to see the published harbour's **M** marker on the map. Start or resume a single-player voyage near the harbour to see it load. Drafts are listed in the Scenery Editor and stay out of normal play. If a draft is missing, check its folder, file name, JSON syntax and `status`. Confirm that the anchor is within the playable world and that every FBX or library ID exists. If models appear below ground, adjust **Z** or use **Snap to ground**. If you edit the model list or anchor in JSON, reopen the draft before using **Save draft**. Full example JSON with terrain placement, custom loaded harbor terrain and bulding placed with the editor.
    1 point
  2. Thanks for the update, mate! I'm trying to import some Hirstshals scenery now. This is just a test for the moment, but I'll turn it into full 3D scenery soon. I'm preparing the layout and ground textures first. It's already getting ready for the Superspeed Ferry Color Line vessel. how it looks like
    1 point
  3. Alpha Version 0.0.17 - Mooring and anchor system is now live - Harbor and boat fenders added - FPS view added Key "3" - Freelock camera added Key "4" - Improved tile chunking for patching - Added user importing watercrafts - GPS window key "G" added - Added moveable parts for watercraft - Watercrafts can now be controlled with 3d steering wheels and throttles - Orbitcam logic reworked - Basic weather menu added Key "T" - Custom buoyancy added (C++ core) - Added low-poly terrain from Calais up to Elbe approach - Increased radar range to 16nm
    1 point
  4. Imported ships can optionally support first-person walking in singleplayer. Ship creators can define an entry point and add simple collision boxes for floors, walls, and consoles. Every time the player enters first-person mode, they return to the configured entry point, even if they walked away from it before switching to the exterior view. Set up walking in the Ship Editor Open your ship in Ship Setup and select FPS setup. Place the FPS entry marker at foot level, on top of the intended floor. Set Entry yaw to choose which way the player faces. Select + Collision box to add a floor. Use the wireframe preview to position, resize, and rotate the box. Add more boxes for walls and obstacles as needed. Turn FPS walking on, select Save JSON, and start a new voyage to test the setup. The entry needs a walkable floor and enough clearance for the player to stand. If the entry is blocked or has no walkable floor, the game keeps the current camera view and shows a message. Configure boat.json directly Add this optional section to your existing boat.json: Positions and sizes are in ship-local centimeters, with X forward, Y starboard, and Z up. sizeCm is the full size of the box. In this example, the floor is 20 cm thick and its top is at Z = 100 cm, matching the entry height. You can add up to 64 collision boxes. Omit firstPerson or set "enabled": false to keep walking disabled. The boxes move with the ship and block the player without applying physical forces to the vessel. In first-person mode, the ship uses LOD 0 and its 3D bridge instruments update normally.
    1 point
  5. Alpha Version 0.0.30 - All terrain tiles packed into container files (90 container files instead of 14.500 single files) - Removed the old single terrain files in conjunction with the new Launcher version
    1 point
  6. Launcher 1.0.12 - New Release for the new scenery streaming system - Terrain is now streamed from container files instead from single tile files - Launcher is able to delete the old single terrain tile files from the game directory
    1 point
  7. Alpha Version 0.0.29 - Test build for scenery container streaming - Test of game structure update for container streaming
    1 point
  8. Alpha Version 0.0.28 - Editor added support for LOD's (LOD 0, LOD 1 and LOD 2) for imported watercrafts - Editor added status messages for FBX import (also if import failed) - Editor added multi FBX file import (all files sharing one polycount-limit of 2 million) - Editor added First Person walk mode for imported watercrafts (preview feature) - NEW, "standby modus" for 3d instruments when selected Orbitcam and Freelook Cam - Test version for new packed scenery files (Plymouth area now packed in a container file)
    1 point
  9. Alpha Version 0.0.27 - New key binding arrow up and down increase/decrease throttle by 5% - New key binding CTRL + arrow up and down increase/decrease throttle engine 1 by 5% - New key binding ALT + arrow up and down increase/decrease throttle engine 2 by 5% - New key binding arrow left and right 1° degree rudder to port and starboard - Fixed overbrighted watercraft lights and wrong water surface reflections with DLSS - Fixed wrong reflections on water surface then using DLSS - Fixed performance bug with the UI and 3d radar instrument - Improved representation of the radar (removed yellow crosses for objects) - Added graphic option for scenery updated to the radar - Reworked Main Menu and Pause Menu - Reworked player UI with UI instruments - New ambient sound zones added also for imported watercrafts - New generator start, run and stop sounds added also for imported watercrafts - Agile added bridge, decks and deckwork lights - Agile added dimmer for bridge instrument lighting - Agile added generator and bridge ambients sounds - Editor added black and white 3d instruments - Editor added generator sounds - Editor added boat ambients sound zones - Editor fixed autopilot not working for imported watercrafts
    1 point
  10. Autopilot For adding an working autopilot to your watercraft via JSON, simply add: "autopilot": { "installed": true } to the JSON file. If you adding an autopilot 3d instrument to your watercraft, the autopilot class is automatically added to your boat. 3D Bridge Instrument Colors 3D bridge instruments are available in White and Black for both Blueprint ships and imported ships. You can set the color individually for each instrument. Select Original to keep the instrument’s existing appearance. Blueprint ships — Select the instrument component and go to Boat → Bridge Display → Face Color. Imported ships — In the Ship Editor, open Bridge Equipment, select an instrument, and set Face color. Save and reload the ship to apply the change. Editing boat.json directly — Set "faceColor": "White" or "faceColor": "Black" in the instrument’s bridgeEquipment entry. Use "faceColor": "Original" or omit the field to keep the original appearance. On analog instruments, the setting changes the dial face and scale markings for contrast. On radar, chart, and control panels, it changes the frame around the display. Night lighting works with both color options.
    1 point
  11. Ambient and Generator Sounds You can now add ambient sound zones and individual generator sounds to your ships. Ambient sound zones Place a BoatAmbientSoundBox component in your ship Blueprint. Resize and rotate the box to cover a cabin, machinery space or deck area. The sound plays at full volume inside the box and gradually fades outside it. Volume, fade distance and fade time are adjustable. Blueprint Box Extent values represent half the box’s total dimensions. Generator sounds Add a BoatGeneratorSound component at each generator’s position and assign its Start, Running and Stop sounds. The running sound plays whenever the generator is running, including when it is disconnected from the ship’s electrical bus. Inner radius, distance falloff, volume and fade time are adjustable. In Blueprints and JSON, Generator Index 0 means the first generator. Imported ships In the Ship Editor, add a Bridge Equipment entry and select: AmbientSound for an adjustable sound zone. GeneratorSound for a generator sound source. Use WAV paths relative to your ship’s folder, such as Sounds/generator_loop.wav. Imported WAV loops repeat automatically. Mono files are recommended for positional generator sounds. The editor displays a cyan preview of ambient boxes. Save and reload the ship to apply sound changes; the placement preview remains silent. Sound playback runs locally on each client. In multiplayer, generator audio follows the synchronized generator state.
    1 point
  12. VSV7

    Dover-Calais ferry

    Currently working on the Dover–Calais ferry Soon in Across The Seas! VSV7
    1 point
  13. MarkoBarthel

    Dover-Calais ferry

    That's awesome, nice to see the first videos made in Across the Seas.
    1 point
  14. VSV7

    Dover-Calais ferry

    ship maneuvering test- Still working in progress
    1 point
  15. You can equip an imported ship with a bow thruster, a stern thruster, or both. Each thruster has its own thrust position and maximum force. You can also place optional water effects at the port and starboard tunnel openings. Set up a thruster in the Ship Editor Open your imported ship in the Ship Editor. Click + Bow thruster or + Stern thruster. Select the Bow thruster force or Stern thruster force marker and place it at the center of the thruster tunnel. Set Maximum thrust (kN) and save your changes. The force marker determines where the sideways force acts on the ship. Its position affects how the ship turns when you apply thrust. Add foam and spray Select the thruster’s force marker. Click + Port water FX or + Starboard water FX to add an outlet marker. You can add either side independently. Move each marker to its tunnel opening on the hull, below the waterline, and save. The outlet markers control where the foam trail and spray appear. When the thruster runs, the discharge side produces the stronger effect. The intake side produces a weaker effect. An outlet placed above the waterline or too deep below the surface may produce no visible effect. Configure thrusters in boat.json Add the following fields at the top level of your existing boat.json. Adjust the example coordinates and force values to suit your model. Positions are relative to the ship and use centimeters in [X, Y, Z] order. Positive X points forward, positive Y points to starboard, and positive Z points up. Port is the negative Y direction. For each installed thruster, positionCm and forceKN are required. portEffectCm and starboardEffectCm are optional. Existing thruster configurations continue to work, and water effects appear once you add the corresponding outlet positions. Operate the thrusters Use the bow and stern thruster sliders in the boat controls. Each slider holds its selected thrust. Double-click a slider to return that thruster to zero. Numpad keys Action 7 / 9 Decrease or increase bow thrust by 10 percentage points 1 / 3 Decrease or increase stern thrust by 10 percentage points 5 Return both thrusters to zero Example JSON text: { "bowThruster": { "positionCm": [410, 0, -80], "forceKN": 12.5, "portEffectCm": [410, -120, -80], "starboardEffectCm": [410, 120, -80] }, "sternThruster": { "positionCm": [-380, 0, -90], "forceKN": 9.0, "portEffectCm": [-380, -150, -90], "starboardEffectCm": [-380, 150, -90] } }
    1 point
  16. Thanks for the update, mate! She’s now much more maneuverable and fits perfectly into the scenery. She’s still a work in progress for now.
    1 point
  17. Alpha Version 0.0.26 - Fixed a bug in the terrain streaming engine - Fixed a bug that caused performance issue then the camera goes underwater - Fixed a bug with FrameGen resets and starts again after closing Pause Menu - Improved loading and unloading of buoys, lighthouses and windparks - Improved handling of loading shoreline waves and effects - Improved terrain material and added settings in the Options Menu - Added thrusters for imported watercrafts via Editor and JSON file - Added foamtrail and spray effects for thrusters for imported watercrafts - Added more smaller houses to the scenery model library - Added over 50 new OSM placed houses to Calais
    1 point
  18. You're welcome VENJS.
    1 point
  19. VSV7

    VSF to Across The Seas

    This is my ship model originally made for VSF. Look how it looks now in Across the Seas! It looks even better, The graphics and overall appearance have improved so much. It just needs a few more adjustments
    1 point
  20. MarkoBarthel

    VSF to Across The Seas

    She looks great, really nice work VENJS.
    1 point
  21. MarkoBarthel

    Dover-Calais ferry

    She looks great, amazing work so far! Looking really forward to see this beauty in the sim!
    1 point
  22. First Multiplayer test is now live. Currently limited to 8 users. Later it will be possible to set up your own multiplayer servers.
    1 point
  23. Alpha Version 0.0.22 - Hotfix version for fixed shadows of the user imported watercrafts - Shadows now working also with Virtual Shadow map for imported ships
    1 point
  24. Testing the new shoreline effect, the effect is working on the whole low-poly terrain.
    1 point
  25. Ahoy Captains, Here is a quick guide for importing you own created watercraft into the sim. I will improve and expand the docs for importing over the dev time. You can you the small car ferry in the Mods/Boats folder as a template. Structure tree of imported models. Propeller and ruder (needs to renamed to rudder, will come with an update) correct naming is needed in your 3d program. Mods/ └── Boats/ └── MyFishingBoat/ ├── boat.json ├── ship.fbx │ ├── Prop1 │ ├── Prop2 │ ├── Ruder1 │ ├── Ruder2 ├── preview.png ├── Textures/ │ ├── hull_basecolor.png │ ├── hull_normal.png │ └── hull_roughness.png └── Sounds/ ├── engine_idle.wav ├── engine_running.wav └── horn.wav Ship Setup —ingame watercraft editor If the naming is correct, the imported folder structure would be regcognized by the sim and the boat will be visible in the boat selection menu. For imported ships is the boat editor available in the boat selection menu. Most of the setup can be done in the editor and only a small part is only needed in the json file. Open and edit 1. Open ship selection, choose a custom ship and press **Ship Setup**. 2. Right-drag to orbit; middle-drag to pan; wheel to zoom. Click the preview for keyboard focus, then use W/A/S/D and Q/E to move the view. Shift increases the movement step. 3. Select a point in the left list or click its marker. Drag an axis (red X, green Y, blue Z), or commit a numerical coordinate on the right with Enter or by leaving the field. 4. **Preview bridge** looks from the configured camera. **Use view as bridge** copies the current preview camera position, rotation and FOV to that point. **Frame ship** returns to orbit. 5. **Save JSON** writes setup to this package's `boat.json`. It preserves unrelated top-level fields, including the existing physics tuning. Known setup objects/arrays are rewritten. Changes apply on the next voyage, not to a boat already running in the world. 6. **Close / discard unsaved** discards unsaved configuration changes. It does not undo earlier saves. The preview has no boat simulation or collision and is destroyed on close. It is currently a standalone/singleplayer authoring tool. The source FBX is not changed by this tool. Before a save, the previous JSON is copied to `Saved/ShipSetupBackups/<id>/boat-<unique-id>.json`. If the manifest changed since opening, the save is rejected: close and reopen Ship Setup. Read-only installations cannot be edited until the mod directory is writable. Backups are outside the Mods directory and therefore are not automatically included in a new package. Propellers and rudders: one FBX, separate objects Recommended authoring convention: - Hull/superstructure: ordinary static objects. - `Prop1`, optionally `Prop2`: individually selectable propeller mesh objects. - `Ruder1`, optionally `Ruder2`: individually selectable rudder mesh objects. Export the objects **together in the main ship FBX**. Do not combine them into one hull mesh. Each name must be unique. Apply export scale/orientation consistently and triangulate. All vertices should remain in the ship's assembled positions. Empty helper nodes are not visible propeller/rudder meshes. The editor dropdown can map other object names; names are matched case-insensitively. Missing, ambiguous or already-used names skip animation rather than preventing the boat from loading. Select **None** when no visual model is available. The physical propulsion/rudder points still work. There is no requirement to supply these meshes immediately. The current ferry can use its existing FBX until the propeller/rudder objects are modelled. Separate extra FBX files are not imported by this version. They can be supported later, but would also need explicit transforms, scale and material paths. Each part has two points: - **Force**: where the existing boat physics applies propulsion/rudder forces. - **Pivot**: the rotation centre of the visible object. It need not equal the force point. `axis` and `direction` control **cosmetic animation**, not an azimuthing thrust direction. The axis is in boat coordinates, nonzero and normalised on save; +X is typical for shafts, +Z for rudders. Use +1 or -1 for direction. **Toggle animation** tests the pivot and direction without running physics. During a voyage, propellers follow engine RPM/drive direction and rudders follow steering input. The native propeller animation speed scale remains 0.2. Two engines split `thrustKN` equally; adding the second engine does not double the configured total thrust. The normal two-engine UI is reused. Mooring and fenders **+ Mooring point** creates a station that works with the existing O / Ctrl+O mooring interface. Set position, label, rope diameter, maximum length and breaking load. Up to 32 stations are supported. **+ Fender** adds a standard small rubber-fender representation (an elongated sphere), plus a separate **rope top** marker. Position the centre alongside the hull and the rope top on the rail/attachment. The wire outline in the preview shows the configured size. Port/starboard chooses the control group; changing the side button also sets yaw to face outboard. Local +X must face away from the hull, +Z up. The runtime component reuses the existing deployment, contact and cosmetic pendulum logic. Its visible rope ends at the fixed ship attachment and it adds no separate rigid-body mass. Up to 32 fenders. Custom fender mesh files and large quay-fender authoring are not part of this ship-setup extension. Sounds and preview images Select **Engine sound** or **Horn sound** to edit sound filenames and attenuation. Files are relative to the boat folder. Use forward slashes, for example `Sounds/engine.wav`; absolute paths, `..` and backslashes are rejected. Empty fields are allowed. A missing/unsupported WAV is skipped with a warning. - Supported audio: uncompressed PCM16 WAV, mono/stereo, 8–96 kHz, at most 16 MiB and 120 seconds each. - Prefer **mono** for spatial localisation. Supply engine start, seamless running loop, engine stop and horn as separate files. The two engines have independent playback cursors but share the configured engine sound position in this version. No sound assets are supplied/generated by the code. - Attenuation inner radius and falloff are in centimetres; volume is 0–2. - Supported selection image: PNG, at most 2048 × 2048 and 8 MiB. When the `preview` field is missing or empty, `preview.png` beside `boat.json` is used automatically. Explicit filenames take priority; an invalid/missing explicitly selected image does not silently fall back to another file. Reopen ship selection after copying an image into the package folder. - **Create preview PNG** captures the current ship-only view without markers to a unique new PNG in the package. Then press **Save JSON** to assign it. Existing images are not overwritten. The generated PNG remains on disk even if you close without saving the configuration; remove unused captures manually. JSON fields (optional extension to schemaVersion 1) Existing schema-1 manifests still load with one physical propeller and rudder and their legacy points. Retain the required legacy `cameraCm`, `propellerCm`, `rudderCm` fields. The editor keeps the latter two in sync with the first array entries. New fields can be added to the existing object; this fragment is not a complete manifest and its coordinates are examples, not calibrated positions for the ferry Positions/sizes are boat-local centimetres (+X bow, +Y starboard, +Z up), **after** the presentation model's scale/offset/rotation. Rotation arrays are pitch, yaw, roll in degrees. These setup settings do not automatically compute hull collision, displacement or stability. Keep the existing tuned values. Imported-ship handling settings Ship Setup now has four English-language sections: **Performance**, **Rudder**, **Heeling**, and **Resistance**. These expose the existing native BoatPawn controls, not a new physics model or automatic copying from a Blueprint boat. Save with **Save JSON**, then start a new voyage. Blueprint boats and the existing imported-ship buoyancy coefficients are unchanged. - Performance: total/per-shaft thrust, reverse thrust, RPM response, thrust exponent, optional low-speed boost, engine-start immersion requirement and speed limiting. - Rudder: angle, actuator speed, lift/force limits, propeller wash and each rudder's physical area. Length and height are full centimetre dimensions; they do not resize the visible mesh. - Heeling: None, Inward or Outward turn heel, strength, maximum angle, response/return times and minimum speed. This is turn-induced heel, not wave damping. - Resistance: lateral grip, three-point resistance and its yaw contribution/weights, plus linear/angular damping. Angular damping affects all rotation, including roll and pitch. An optional `handling` object uses the exact C++ property names shown below each control. Only edited overrides are stored. **Default** removes that override and restores the native default; per-shaft thrust instead falls back to an equal share of root `thrustKN`. Root `thrustKN`, `linearDamping` and `angularDamping` are saved from their own controls. Second-shaft/second-rudder settings require two corresponding attachment entries. Native force values are Unreal force units: **1 kN = 100,000 UE units**. Example fragment (illustrative values): Import limits and feedback The Ship Editor shows the imported vertex count for each file and for the assembled model. Each FBX file can be up to 256 MiB. The main model and all additional parts share a limit of 2,000,000 imported vertices. Each optional LOD FBX is checked separately against the same vertex limit. The imported vertex count can be higher than the count shown in your modeling software. UV seams, hard edges, and separate material sections can increase it. If a limit is exceeded, the import message shows the measured value and the applicable limit. Protected export currently supports a single main FBX. Optional LOD files are omitted from the protected package. A multi-FBX ship must be merged into one FBX and its mesh assignments updated before protected export.
    1 point
  26. Imported Ships — LODs, Multi-FBX Models, and Bridge Displays Optional LOD models Imported ships can now include up to two simplified FBX models. The existing model file is LOD 0, the full-detail model used on the bridge and in close-up views. In exterior views, the simulator selects a detail level based on the ship’s apparent size on screen. Add either or both of these optional fields to your existing boat.json: Place the FBX files next to boat.json. Export them with the same origin, scale, and axis orientation. If an optional LOD file is missing or cannot be loaded, the simulator uses an available detail level and records the reason in the log. Assigned rudders, propellers, radar antennas, lamps, and controls keep their original meshes when the hull switches LOD. Leave those meshes out of the simplified hull files to avoid duplicates. Optional multi-FBX models You can assemble a ship from a main FBX and up to eight additional FBX files. This lets you keep the bridge, deck equipment, or other assemblies in separate files while using the same ship physics and controls. Each part needs a unique lowercase ID. Use the same ship origin, scale, and axis orientation for every file. Every listed part must be present for the ship to load. Meshes from a part appear in the Ship Editor as partId::MeshName. For example, an object named Radar in the bridge part can be assigned to a radar antenna using "mesh": "bridge::Radar". Main-model mesh names keep their existing format. Additional parts remain visible at every hull LOD. Simulator-driven animations, such as rudder movement and radar rotation, continue across LOD changes. JSON parameters that can be used for adjusting the physics for your custom watercrafts. Performance - Total thrust fallback (kN): Total propulsion force, divided equally between the configured propellers unless individual thrust values are set. - Max Forward Thrust / Second Max Forward Thrust: Maximum forward force for each propeller. These use Unreal force units: 100,000 units = 1 kN. - Reverse Thrust Scale: Reverse power relative to forward power. For example, 0.5 provides 50% reverse thrust. - Engine Idle / Maximum RPM: The engine’s idle and maximum operating speeds. - RPM Acceleration / Deceleration: How quickly engine speed increases or decreases. - Use RPM Based Thrust: Makes propulsion depend on engine RPM. - Propeller Thrust Exponent: Shapes the power curve. Lower values provide more thrust at partial power; higher values make the response gentler. - Low Speed Thrust Boost: Adds extra thrust at low vessel speeds. The multiplier controls its strength, and the fade-out speed determines when it disappears. - Safe RPM Direction Change: Requires the engine to slow down before changing between forward and reverse. - Maximum Speed: Sets the speed limit in knots. The limiter start fraction determines when thrust reduction begins; the hard limit prevents further acceleration beyond the limit. - Propeller Immersion / Start Requirement: Controls how deeply the propeller must be submerged to permit engine starting. - Thrust Height Relative to COM: Vertical offset of the thrust application point from the centre of mass. Changing this can affect pitching under power. Rudder - Maximum Rudder Angle: Maximum steering angle in degrees. - Rudder Actuator Delay / Movement Speed: Enables gradual rudder movement and sets its turning speed in degrees per second. - Rudder Length / Height: Defines the physical rudder area. Larger dimensions generally produce stronger steering forces. These values do not resize the visible model. - Rudder Lift Coefficient: Controls the rudder’s hydrodynamic effectiveness. - Maximum Rudder Force: Caps the force generated by the rudder. - Water Density: Density used for rudder-force calculations. - Propeller Wash: Adds the effect of propeller flow over the rudder, improving steering at low vessel speeds. Its speed and fade-out settings control the strength of this effect. Second-propeller and second-rudder settings require corresponding attachment points. Heeling These settings control leaning during turns, not wave-induced rolling. - Turn Heel Direction: None disables turn heel, Inward leans into the turn, and Outward leans away from it. - Turn Heel Strength: Scales the amount of leaning. - Maximum Turn Heel: Limits the heel angle in degrees. - Heel Response Time: How quickly the ship leans into a turn. Longer times give a slower response. - Heel Return Time: How quickly the ship returns upright after turning. - Minimum Heel Speed: Vessel speed below which turn heel is disabled. Resistance - Lateral Grip / High-Speed Lateral Grip: Controls resistance to sideways movement. - Maximum Lateral Resistance Force: Caps sideways resistance. - Three-Point Lateral Resistance: Distributes resistance between the bow, midship and stern. - Longitudinal Coverage: Controls how far apart these resistance points are along the hull. - Yaw Scale: Controls how strongly distributed resistance opposes turning. Lower values allow the ship to continue turning longer after the rudder returns to neutral. - Bow / Midship / Stern Weights: Adjust the relative contribution of each resistance point. - Linear Damping: Reduces movement in all directions, not just sideways. - Angular Damping: Reduces rotational movement, including turning, rolling and pitching. Excessive values can make the ship feel unnaturally stiff. Units and defaults Distances are in centimetres, angles in degrees, times in seconds, and vessel speeds in knots, unless the field specifies otherwise. Default removes an individual override. It restores the built-in fallback—not your previous custom value. Existing buoyancy settings remain unchanged unless edited separately.
    1 point
  27. Hello Marko, I had the chance to try Across the Seas Launcher 1.0.10, and I’m quite impressed with it, especially considering that it’s still in alpha. The sea and weather physics already feel very realistic and give a great sense of being on the water. It’s clear that there is a lot of potential here, and I’m looking forward to seeing how the simulator develops over time. Keep up the great work, and best of luck with the project!
    1 point
×
×
  • Create New...