Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[hhrhhr]

then i can't use animation. for example, this is front suspension for buggy, it contains 7 mesh and 4 bones:
 

sample script:

Code: [Select]

    // animate suspension
    var whl = this.wheel(0)
    var sin = whl.saxle;
    //var cos = whl.caxle;
    var rot = whl.rotation;
    var ang = Math.asin(sin);
    body.rotate_joint_orig(ha_fl, rot, {x: 1, y: 0, z: 0});  // half-axle
    body.rotate_joint_orig(ag_fl, ang, {x: 0, y: -1, z: 0}); // A-arm
    body.rotate_joint_orig(tl_fl, ang, {x: 0, y: -1, z: 0}); // top link
    body.rotate_joint_orig(hb_fl, ang, {x: 0, y: 1, z: 0}); // hub
   
    body.rotate_joint_orig(wg_fl, ang, {x: 0, y: 1, z: 0}); // anti-roll wheel group
    body.rotate_joint_orig(bg_fl, steer_fl, {x: 0, y: 0, z: 1}); // steer block
    body.rotate_joint_orig(sl_fl, steer_fl, {x: 0, y: 0, z: -1}); // steer link
    body.rotate_joint_orig(at_fl, ang*AT, {x: 0, y: -1, z: 0}); // top amort
    body.rotate_joint_orig(ab_fl, ang*AB, {x: 0, y: 1, z: 0}); // bottom amort

    body.rotate_joint_orig(tr_fl, rot, {x: 1, y: 0, z: 0}); // trans

if all this meshes will be at one "level", then i can't animate this simple A-arm suspension:

[ZeosPantera]

Keep doing what you are doing hhrhhr.. Looks magnificent.

[deathevor]

Ooohhh. That's... Just, damn... It's....
(Don't have any words)

[PytonPago]

Godda take some of your ideas for my modells ! Werry interesting indeed. 

[ZeosPantera]

My hope is all cars model their full suspension components like this. Even if hidden.

[PytonPago]

My hope is all cars model their full suspension components like this. Even if hidden.

Isnt that the min. prop. for the future of Outerra ? 

  ... Cameni, i just came to a interesting phase of my Ural-4320 - actually i do a pre-model of the basic truck before playing whyte the BM-21 Rocket Launcher. As the variations of those trucks by the same wheel-basis is great, i just thought to ask: is there a plan to make variable models for the further future in OT ? - like hawing a set of car-parts as different objects, that would be possible to combine in the spawn menu (or in a special one). My actual thought is about a variation of bumpers, truck-cages, wheels, maybe even more complex functional parts (like switching between the transport-cage and BM-21 system on the back of the machine, or adding/taking away the gearbox-connected towing device) ... The model would so have some spec. places defined (could be picked at the import menu aside of wheels maybe in a separate window) for several types of those part and parts would be just different models whyte a pre-defined name type for each of those places in the primary model defined ... would make some building/modulable vehicles easier to make and  to update whyte new parts while model space-saving. Aviation-fanclub could use it to change and add new ordnances to models too ...

[PytonPago]

... no need to hurry whyte it of course : ) ...

[cameni]

Normally it's done by creating a model that contains all the parts, and enabling/disabling these dynamically. It's also much simpler than actually trying to connect object dynamically and functionally, although that will be needed too, for trailers and such stuff.

[Midviki]

Does anyone know what is the value maximum possible accepted of .DDS texture on the imported objects?



- Has anyone tested it?

- What circumstances you can use it in a higher improved state?

- And if it is not yet possible, how soon it will be possible to have a higher quality of the texture?

Cause I have 8000x8000 textures.. that looks on the model just exactly like it would be the 2000x2000 resolution.No improvement whatsoever.Or even if I used the 2000x2000 one it looked worse than it should.I am thinking of trying to map it with  16000x16000 resolution, but I'm not sure if it is worth it, taking in account that it took me like 20-25 minutes to render the 8k x 8k texture, and this one would take 4x times longer... Or maybe if I make a bit of research how to render it with the GPU and not the CPU it will go faster, but dunno, till then... the .DDS improvement would sound like a more satiable idea, memory wise speaking.

The first option.. the :  "DXT1              RBG       4  bpp   |   no alpha"  ... lowers the quality from the original state of the texture.

[Juggernautz]

Under image settings, make sure compression quality is set to Production or Highest. That's the only thing I can think of that might be causing lower quality textures.

[mLichy]

Currently we support 4 LODs, these LOD parents names have to start with LOD0.., LOD1..., LOD2..., LOD3..., COLLISION... the last will be used as a collision mesh.

For Collision, we put the geo under a Collision Node/Parent.  But, how are the wheel collisions checked?  Is that still using the render geo? 

Right now I have not setup a custom collision, and I "think" the chassis is not colliding with anything, but need to test again. 

Thanks!

[cameni]

Right now the bounding box is used for the collision, and it doesn't collide with the terrain yet, only with other objects.

Wheels use a separate collision checking, ray vs. terrain.

[mLichy]

Ah ok. Cool. Makes sense. Thanks!

Oh, on a side note, where do I find the tetra material file?

[cameni]

You mean Tatra? Stock vehicles are in packages folder, but in the program directory, not data.

[mLichy]

Oops yeah. Ok great. Thank you!