Oolite Bulletins

Killer Wolf wrote:

not sure what you mean by it "jumping positions" - i'm assuming it's just a view thing, and not that it's actually moving.
as for placement, i have this issue myself as position coordinates in my modellers don't match Oolite's measurment unit; i find placement of exhausts especially time-consuming. i think Wings3D is the closest match. as it is, i get the modeller coordinates, put those in then just repeatedly tweak them as necessary in-game.

Killer Wolf wrote:

i can't understand the Blender axis being wrong, i've used a load of modellers and never come across anything like that. i have no idea what the "vibrating" could be either, i've never come across anything like that.
could you post a few screen grabs or something?

Commander McLane wrote:

This looks like a case of inverted normals. A dock is essentially a concave structure, you're watching it from the inside, not the outside. Therefore the normals have to point inwards. What you're seeing is the odd-looking, pseudo-transparency effect you get with switched normals.

As soon as you have inverted the normals, the front end of the dock should match the center of the hole in the ship texture. (Example: the Coriolis extends from [0 0 500] to [0 0 -500]. The dock is placed at [0 0 500].)

Griff wrote:

you don't have "initialize_turret" or anything written inside your docks entry in the shipdata .plist? i remember something similar happening to one of my ships and it turned out i'd made a copy & paste error between a dock and a turret- result was a weirdly rotating dock placed a few meters outside the main hull of the station!

{
                        type = "standard";
			is_dock = "true";
			subentity_key = "andricodred_dock";
                        port_dimensions = "931.072 x 284.350 x 666.750";
                        tunnel_corners = "4";
			position = (0.0, 242.3, 635.8);
			orientation = (1, 0, 0, 0);
			}

"andricodred_dock" = {
		"ai_type" = "nullAI.plist";
		"model" = "andricodreddock.dat";
		"name" = "andricodred_dock";
		"roles" = "andricodred_dock";
        };

Zieman wrote:

If you have other subentities present, the order of entries in shipdata.plist matters.
This sequence works:
dock
'regular' subents
subents with guns (not completely sure if this should be before 'regular' ones or not)
turrets
flashers

Zieman wrote:

I had similar displacement problems when I started making Far Arm ships Titan, and the solution was to move those displaced subents up in the .plist, to reside there before turrets.
So, I'm pretty sure your problem goes away by just moving the dock-entry up in your shipdata.plist, like this:

Code: Select all

		subentities = 
			(
			"example_dock 0 0 -850 0 0 1 0",
			"example_subent_a 0 0 360 1 0 0 0",
			"example_subent_b 0 0 375 1 0 0 0",
			"example_turret 79.55 192.05 314.0 0.8451 0.4978 -0.0990 0.1681",
			"*FLASHER* 0.0 0.0 650 240 0 0 64",
			"*FLASHER* 0.0 0.0 -750 270 0 0 200"
			);

mandoman wrote:

Code: Select all

{
                        type = "standard";
			is_dock = "true";
			subentity_key = "andricodred_dock";
                        port_dimensions = "931.072 x 284.350 x 666.750"; <------ three decimal places
                        tunnel_corners = "4";
			position = (0.0, 242.3, 635.8);
			orientation = (1, 0, 0, 0);
			}