After doing a bunch of short-range warps, the crew was fine and disengaged the drive in the "Oort cloud" as expected. However, on a long range warp, the crew kept going and slammed directly into the star instantly disintegrating the ship. My guess is that over longer distances, warp and coordinates become imprecise, causing the crew to not disengage within safe distances

specifically the 'Info" column.
when sitting at the capitol building trying to build a city from the capitols building window, the window doesn't refresh when buildings have finished being built, or if you've changed "Employ Citizen" checkbox.

The walls around a ringworld have no collision model and avatars can just walk off into space. Additionally, anything that touches the back of a ringworld is teleported through it, to ground level.

And finally, the first and third person (not overhead) views are broken while near the backside of a ringworld. My viewport was hundreds of meters behind my head after getting out of a fighter to do some testing.

A couple of new tools added to the designer would help tremendously with usability.

The first is an automatic room void tool.

Now I know a room void "button" has been debated against and makes good sense as to why it will never be added.

Which is why I think a tool would be best instead. The method of implementation I am thinking is a polygon based extrusion tool. Simply put, the user would draw a polygon on the grid extrude it to height and a hull void would generate 0.1 smaller than the room relative to each face. This room would have simple square walls be a pure polygon, all convex sides, on the floor and ceiling, and could even have a fixed number of edges for the source polygon and subsequent walls as decided based on the necessary limitations of the pathfinding mechanics. This tool call it room+room void extrusion would allow people to draw full corridors and rooms using the current designer quickly and easily.

The next idea, Doors, two tools air tight and not airtight. 

Not airtight doors could be added by drawing a line from one room wall to the other and setting a wall thickness this auto generated door would be a three piece mesh with three barriers. Two static and one barrier/mesh tied with the door state. This door would exist within the room void meaning it would not isolate them when opened or closed.

The next tool should be the air tight door. This would be a simple auto door tool that would require one to draw a polygon on one wall like the door jig and then have it cut the door with some simple checks in place both walls need to be squares, parallel and be less then 0.5 meters away. This auto door tool would automatically add the door and associated walk path and room void.

It should project a breathable atmo around the hull, akin to a fancy skinned biodome.
It all should protect against all environment damage, Corrosion, Pressure, and excess speed. Making entering corrosive and Insidious atmospheres easier as well as helping with aerobraking all at the expanse of sweet sweet power.

My client instantly closes during every system transition. It's happening in both Hazeron Commander and the main client.

Win64 Build

Hello

The Helicopter Controls for "Turn Left" and "Turn Right" are ignored when there is a Joystick Axis Configured to act as Turn Axis Left and Right.
Unbinding the two fields in the Joystic Collumn fixes it and the Turn Left and Right buttons are used again.

As title says. After 10.09.20/11.09.20 update i cant enter designer both online and offline.
Launcher simply locks up. "Enter designer" button in game does nothing
Win64 build

Hello,
I was wondering if you could supply a basic spec on how the SoH format is constructed. The spec doesn't need to be super detailed, but information about if it's compressed (and what algorithm is used), general structure of the file like vertex data, then uvs, then index array, then normals, etc.

I tried reverse engineering the format myself but the furthest I got was figuring out that the first 2 bytes were likely a version identifier, next 4 bytes are an int denoting the size of a data blob, and then the rest of the data blob is mostly unknown. There's a good chance that the first 4 bytes of the data blob are also a version identifier but there's no way to really tell. All of the data seems to be strewn about in a way I can't really glean from trial and error, and even something as simple as changing a single vertex changes a ton of the data.

I tried using the designer multiple times but i'm just over it not working the way i want it to, and having to deal with manually texture mapping every individual face since everything is bugged, and it is actually far easier for me to bypass it entirely by creating tools to export/convert from other editors. I would really like to be able to contribute nice looking buildings/ships that other people could use but unfortunately it's just an absolute pain to do anything other than an untextured blob at present.

Ideally it would be nice if you could implement gltf/glb importing as well, since STL is an ancient format that isn't particularly useful for anything, and/or fix the 3DS import to actually properly respect UVs instead of shoving them off way into the corner randomly (although i'd still have to use an external converter to go from GLB->3DS), that would also be great.

Thanks

As on the tin, often a ship with an officer will ignore the wormhole when ordered to travel by wormhole to a system, and deadhead instead.