Page 2 of 3
Posted: Wed Aug 08, 2007 10:26 pm
by Griff
Commander McLane & Charlie
Thanks for the info about quaternions!
I've been trying to write out a simple spreadsheet that would combine any two quaternions from that table that you linked to charlie using the formulas from Commander McLane's post and display the result, it seems to be working with the 180degree stuff but i'm not sure what values i should be typing in for the 90degree stuff, the table just puts "sqrt(0.5)", should i type in 0.5 or the squareroot of 0.5 or what?
here's a screenshot of the spreadsheet
you just work out which two quaternions you need from the table, type them into the two red rows in the spreadsheet and you get the required quaternion in the yellow box - well, at least that's the plan.
Edit D'oh should have checked the wiki, i found a page that gave the formulas on how to generate quaternions around a single axis for any angle, i've added that into the spreadsheet so it should now be possible to generate single axis quaternions for any angle and axis and combine them in the multiplier.
I've uploaded it here:-
http://www.box.net/shared/l31tyj4i39 14Kb
It's been put together in Excel in Microsoft Office2003, but hopefully openoffice should be able to open it too, i've saved out an excel95 and an excel 97 version too.
Docks
Posted: Wed Nov 25, 2009 9:09 am
by Killer Wolf
Right, just to clarify what i've learned from building my Nuit station...
if you wanna do a new fancy-looking dock :-
- i used dock-flat.dat as a template for sizes : use your modeller to create a box of the same size/shape, and then delete the front face, ie the entrance. Then turn the goddamn thing inside out, or you won't be able to see it.
this box has to be modelled at the origin, (0,0,0). This is the important bit that was doing my head in. for some reason Oolite seems not to recognise a displaced dock model - you have to create it where it expects it to be, and then tell it in the OXP that it has been moved :-/
- do the usual stuff, skinning, DAT converting etc. your ship/station model should obviously have a gap in its wall/hull the same size as the dock entrance.
- in your OXP shipdata plist, the dock will be included as a subentity of the ship/station. give it a name that includes the word "dock", and use the positioning variables to shift the model from the origin to its correct place; this may take a bit of trial and error.
eg:
" subentities = (
"dock-nuit -11.5 3004 421 1 0 0 0","
- the dict definition itself is straightforward. i gave mine the word "dock" in its role too.
and that's basically it.
EDIT - Not sure if this is new during my absence or i just previously avoided it by chance, but on testing a new game asset it turns out that the main game item needs "station" in its "roles" attribute ~ i spent a while wondering why my asset wouldn't rotate and the dock wouldn't work, until i added that alongside my custom role.
Posted: Sat May 01, 2010 12:08 am
by ADCK
Hah, wish I knew about this thread earlier, I learnt most of the stuff in this thread through trial and error, I had things like docks appearing inside out, facing weird directions, not working at all, upside down, etc.
But now I get the docks working all the time hehe.
preferred properties of mission screen background images?
Posted: Sun Feb 17, 2013 12:02 pm
by GGShinobi
Hello everybody,
This might not be the best place to put this question, but I didn't find any better one. So here it comes:
What are the preferred properties for mission screen background images?
More precise, I'd like to know:
- what formats are supported (.png, .jpg, ...) and which is the preferred one?
- is there an optimal resolution? (from an error message I learned that length and height should be dividable, e.g. 1024*512)
- any other things to keep in mind?
I'm currently using some self-made images in .png-format and 1024x512 resolution. But they make the oxp rather big...
Should I use .jpg and/or lower resolutions instead?
Thanks in advance for all your answers!
EDIT: corrected typo
Re: preferred properties of mission screen background images
Posted: Mon Feb 18, 2013 9:02 am
by Commander McLane
GGShinobi wrote:- what formats are supported (.png, .jpg, ...) and which is the preferred one?
PNG only.
- is there an optimal resolution? (from an error message I learned that length and height should be dividable, e.g. 1024*512)
As you already found out, all dimensions must be powers of two. So, for a rectangular picture, you could also use 512*256 or 256*128. For a square picture, you should be fine with 512*512 or 256*256.
- any other things to keep in mind?
At least as far as texture PNGs are concerned, they
must not be saved in interlaced mode. I don't know whether this is as strict a requirement for background images, but it certainly doesn't hurt to save them non-interlaced.
Re: preferred properties of mission screen background images
Posted: Mon Feb 18, 2013 12:50 pm
by GGShinobi
McLane, thank you very much for your answers! They helped me alot!
Commander McLane wrote:GGShinobi wrote:
- is there an optimal resolution? (from an error message I learned that length and height should be dividable, e.g. 1024*512)
As you already found out, all dimensions must be powers of two. So, for a rectangular picture, you could also use 512*256 or 256*128. For a square picture, you should be fine with 512*512 or 256*256.
Didn't know that!
I misinterpreted it that the numbers must simple be dividable (so I thought it would have been possible to do a 1000x500 pic or so)! Thanks alot!
This will help me to considerably reduce the size of my oxps!
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Thu Nov 05, 2020 1:35 am
by Reval
If there's one thing I'm absolutely useless at it's wrapping my head around axes (ie. which of the three values represents forward, which aft, which up, which down, etc.)
I mention this shortcoming because I'm currently needing to adjust slightly the forward and aft views of (normally) unflyable ships like the Gecko, Krait and Mamba. Oh, they fly just fine, but there are glitches in the forward and aft views - remnants of the 3D model, I think. And since these ships were never designed to be played, no one thought of including sensible view_position values.
Also, I'm still not quite sure which properties I'm supposed to edit to get a decent forward/aft view. There's this part:
Code: Select all
custom_views =
(
{
view_description = "Rear View";
view_orientation = "1.0 0.0 0.0 0.0";
view_position = "0.0 15.0 -100";
weapon_facing = "FORWARD";
},
{
view_description = "Rear Right View";
view_orientation = "0.9239 0.0 0.3827 0.0";
view_position = "70.71 15.0 -70.71";
weapon_facing = "FORWARD";
},
{
view_description = "Right View";
view_orientation = "0.7071 0.0 0.7071 0.0";
view_position = "100.0 15.0 0.0";
weapon_facing = "FORWARD";
},
{
view_description = "Front Right View";
view_orientation = "0.3827 0.0 0.9239 0.0";
view_position = "70.71 15.0 70.71";
weapon_facing = "FORWARD";
},
{
view_description = "Front View";
view_orientation = "0.0 0.0 1.0 0.0";
view_position = "0.0 15.0 100.0";
weapon_facing = "FORWARD";
},
{
view_description = "Front Left View";
view_orientation = "0.3827 0.0 -0.9239 0.0";
view_position = "-70.71 15.0 70.71";
weapon_facing = "FORWARD";
},
{
view_description = "Left View";
view_orientation = "0.7071 0.0 -0.7071 0.0";
view_position = "-100.0 15.0 0.0";
weapon_facing = "FORWARD";
},
{
view_description = "Rear Left View";
view_orientation = "0.9239 0.0 -0.3827 0.0";
view_position = "-70.71 15.0 -70.71";
weapon_facing = "FORWARD";
},
{
view_description = "Top View";
view_orientation = "-0.7071 0.7071 0.0 0.0";
view_position = "0.0 100.0 -10.0";
weapon_facing = "FORWARD";
},
{
view_description = "Bottom View";
view_orientation = "0.0 0.0 0.7071 0.7071";
view_position = "0.0 -100.0 -10.0";
weapon_facing = "FORWARD";
}
);
and this one:
Code: Select all
view_position_aft = "0.0 5.0 -22.5";
view_position_forward = "0.0 3.5 17.4";
view_position_port = "-12.0 1.5 -1.0";
view_position_starboard = "12.0 1.5 -1.0";
If anyone could enlighten me, my developing migraine would be eased
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Thu Nov 05, 2020 2:26 am
by Commander_X
I'd guess a quick answer would be that if you change the last set of them (view_position_[aft|forward|port|starboard]), you'd change the camera position for the views you get when hitting 1/2/3/4 or F1/F2/F3/F4 keys (that is the cameras along the weapon positions). The first set would change the camera position you get when switching to the "outside" cameras (that looks _at_ the ship) when consecutively hitting the "v" key.
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Thu Nov 05, 2020 2:36 am
by Reval
Ah right. Many thanks. I'll start with the basic 1,2,3,4 views and maybe later move on to the external views. But could you tell me which of the three values I should adjust for Fore and Aft? and should I decrease or increase them to get rid of the 3D artifacts?
I'm looking to get sensible views out of the portlights of the Gecko, Krait, Mamba, Sidewinder, and Viper.
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Thu Nov 05, 2020 3:03 am
by Commander_X
I'm no expert, but from the looks of them, I'd say that considering each coord set a position of values "x y z" relative to the ship's center/origin (hint: 0 on the first position for aft and forward implies centered on the x -- that is left/right -- axis), what you'd need would be to increase the z value for the forward position and to decrease the z value for aft, thus your original:
Code: Select all
view_position_aft = "0.0 5.0 -22.5";
view_position_forward = "0.0 3.5 17.4";
would become:
Code: Select all
view_position_aft = "0.0 5.0 -23.0";
view_position_forward = "0.0 3.5 18.0";
This would be an example on how I'd expect the cameras to be "pushed" to the exterior of the model, thus avoiding the artifacts. You'd need to experiment with the values, I have no clue if the values I've used here bring any visible enhancement.
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Thu Nov 05, 2020 3:07 am
by Reval
So grateful to you for that life-saving pointer, commander!
Actually, the properties I posted as examples were from the Adder, since my new flyable ships do not yet have entries.
So I'll tinker, and thanks again
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Fri Nov 06, 2020 2:23 pm
by GearsNSuch
Something I’ve found helpful is to import the model in to a program such as Blender, position the cameras in there, and copy the coordinates. It gives a somewhat accurate preview without the hassle of reloading. Do be warned that Blender swaps the Y and Z axes, and they may be inverted.
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Fri Nov 06, 2020 10:24 pm
by Reval
Thanks you! (but Blender is just the kind of program that has me breaking out in hives - maybe I'll give it a go, though; conquer my terror
)
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Fri Nov 06, 2020 11:54 pm
by Reval
I've provisionally tied the new ships' views to the weapons positions (with minor adjustment to Aft view in the case of the Gecko and Viper). But there's an oddity now: Although I can see laser hits on targets (bits of wreckage flying off etc) I do not see the actual beams of the weapon.
It appears I'm blocking the fire somehow by being plunked down on the gun-barrels. I'm guessing I should apply an offset for the view, but how much and in what direction?
Code: Select all
{
"gecko-player" =
{
like_ship = "oolite_template_gecko";
roles = "player";
view_position_forward = "0.0 -2.49055 25.6416";
view_position_aft = "0.0 5.54957 -25.1558";
view_position_port = "-13.75 -2.0625 -1.875";
view_position_starboard = "13.75 -2.0625 -1.875";
};
"krait-player" =
{
like_ship = "oolite_template_krait";
roles = "player";
view_position_aft = "0.0 0.0 -34.6";
view_position_forward = "0.0 -1.6045 41.5081";
view_position_port = "-45.0 0.0 -13.5";
view_position_starboard = "45.0 0.0 -13.5";
};
"mamba-player" =
{
like_ship = "oolite_template_mamba";
roles = "player";
view_position_aft = "0.0 1.5184 -30.3193";
view_position_forward = "0.0 0.241963 33.558";
view_position_port = "-16.5 -3.0 0.0";
view_position_starboard = "16.5 -3.0 0.0";
};
"sidewinder-player" =
{
like_ship = "oolite_template_sidewinder";
roles = "player";
view_position_aft = "0.0 -6.5 -17.5";
view_position_forward = "0.0 -2.764625 25.2155";
view_position_port = "-24.25 0.0 0.0";
view_position_starboard = "24.25 0.0 0.0";
};
"viper-player" =
{
like_ship = "oolite_template_viper";
roles = "player";
name = "Viper Mk 1 FE";
view_position_aft = "0.0 0.0 -27.5";
view_position_forward = "0.0 -0.15 35.0344";
view_position_port = "-12.5 0.0 0.0";
view_position_starboard = "12.5 0.0 0.0";
max_cargo = 25;
likely_cargo = 12;
};
"viper2-player" =
{
like_ship = "oolite_template_viper-interceptor";
roles = "player";
name = "Viper Mk 2 FE";
view_position_aft = "0.0 0.0 -32.0";
view_position_forward = "0.0 -0.15 35.034";
view_position_port = "-23.75 0.0 -1.75";
view_position_starboard = "23.75 0.0 -1.75";
max_cargo = 30;
likely_cargo = 15;
};
}
Re: Things I Wish I Knew BEFORE Starting this *@*#~&ing .oxp
Posted: Sat Nov 07, 2020 12:30 am
by dybal
I usually offset at the y axis (that's the second number), the smallest amount that gives you enough paralaxe to see the beam, but not enough to make you have to put the cross-hairs high on the target to hit... try 2 (depends if you are scaling the model in the shipdata), and I prefer to have my viewpoint above the gun (yours are below the centreline, there are plenty of negative numbers)