Messages

size_x = 936.3456
size_z = 234.0864
scale = 30

In Mapview & Tracked only shows left half of map in surface mode
and right half is discolored in materials mode

In 3d mode in mapview,Tracked, and ingame only renders when looking in a certain direction.

This is a really fun little track, the offset berms are really fun, and the whole track flows really really well after a couple laps, real 250f friendly.


The tiny double (after the whoops with the turn in it and before the booter to table top) the inside of the turn Before and after could use a little a bit of a rut or a line, just looks a little blank there. Mostly before though.

Some spots/sections need smoothing(especially the 2 bigger whoops)

The environment could use somethings like Volcano/mountain, ocean, beach, river/stream, bridge, waterfall, jungle

In the 3rd person view the finish line banner seems a bit low.

re-reference the new file in the program or
save the desired file with a new name and re-reference it or
Sometimes you have to manually delete the texture file through the editor, then replace it with the new one.
Other times you'll have to MANUALLY copy the entire model wireframe and add the new texture file(s)

3Dmax references a lot of internally saved files. After a while it just assumes you're referencing the same unedited file and you have to create a new file to reference the edited file, It's been an issue for a longtime. If you're not careful it'll go ballistic and turn into the Terminator.

Canada, Between Houses (gonna maybe be in Ontario or Québec, IDK real estate agents are jerkoffs), 25

Used to eat those sugar packets you're supposed to put in the coffee and Alpine-Ski and play Hockey.

X-games/Vans Triple Crown sealed the deal fo me, mcm2/MTX:mototrax was where it's at (The Big Table to Gap to Mellow Landing on the the St louis SX track was frickin ridonculous to clear.) then mvaU, mvaR, mvaA, then finally submitted to the Sim, Now here after 5 Dirt/MX bikes and a Street bike(+ cars, trucks, tractors, skidsteers, go karts, and Tonkas, and the Bigwheel, and bikes/tricycles) Crusty Demons and Nitro Circus and the infamous Fresno Smooth got me through the Injury, still can't through a ball worth a damn though, lol.

IMHO

I feel the 450f to be very very under-powered right now, it's WAY LESS powerful than the 350f AND 250f from beta3. I'm really dissasspointed with the horse-power, I had a few sickass tracks that I was nearly ready to beta release which rode great with the 250f and 350f in Beta3, but now I can't even clear any of the main jumps with the 450f.
Maybe it's a difference of EURO specs vs USA(and most of CANADA(at least the cool kids that don't use metric(lol))) specs. Maybe it's the Gyro rigged backwards, IDK I'm not a computer rocket scientist.

I REALLY like how much better the new(ish) physics of Beta4 react, but the power is just abysmal, it's like trying to ride a TTR on a PRO motocross track, or a 2-stroke without a jet fuel additive on that track.

Beta 3 was alright for power, but still seemed like the bikes were under-powered and using the lowest grade pump gas. I built an in game distance jump test, and was jumping nowhere near as far as I could(in real life) on a 10 year old 250f, running 94 pump octane.

(Most MX Riders that I know run straight MX Race gas or at least mix a little of it into their pump gas, or mix in a little aviation gas, or add the jet fuel additive.)

Maybe it needs to simulate a larger amount of force absorbed by the ground?

Force it takes to bend parts like the wheels, suspensions, and frame and the force it takes for it to return to it's original shape?

I don't think anyone's computer could handle all that in real time, but something really pre-calculated might work?

Si vous parlez d' oculus rift c'est là http://forum.mx-bikes.com/index.php?topic=684

Si vous parlez du vu en 1ière personne sur votre écran d'ordinateur, il y a un boutton qui doit être appuyez ( vous pouvez changer quelle bouton, en la menu d'options.)

Peut être ça ici http://forum.mx-bikes.com/index.php?topic=954 aller vous aider, si vous n'avez pas déja installer la traduction français.

J'espère que ça aide.

Fats, i have a issue with l3dt.
if i import my heightmap.raw it doesnt read it right, when i convert it to .png i can import it and work on it but it´s stepped like this.


Any tips?
to export it is fine, works great.
i´m digging the terramodeling tools, if it had a better viewport performance would be a great program.

I looked at the L3DT forums and found this
http://www.bundysoft.com/phpBB2/viewtopic.php?t=793

and this
http://www.bundysoft.com/docs/doku.php?id=l3dt:formats:specs:raw#mode


It says "In the Export Wizard you should press options, and set it to RAW and 16-bit unsigned (full range)"


I've never used the program though, so I can't be of much help.

I like this trail, so tight

I'll try and give some help on texturing and material layers

First The base layer doesn't need a thickness, all layers on top of it do.
All textures and masks must be a power of 2.

To create a mask it must be set to 8bit colours and saved as a 32bit image and should be a '.TGA'
you need to add an alpha layer
needs to be in greyscale

The RGB layers are completely ignored.
The Alpha Layer is the only one used

White = 100%, Black = 0%

For textures it affects the transparency/opacity (White = Visible, Black = Invisible)

For material layers it affects the thickness ( a layer with a thickness of 1.0 metre and the mask at 75% grey would make that area 0.75 metres thick)



Here's some sample code to help out.


Track.hmf

Code Select Expand

num_layers = 4

layer0
{
map = dirt_dark.tga
repetitions = 32
}

layer1
{
map = dirt_light.tga
repetitions = 32
thickness = 0.03
}



layer2
{
map = grass.tga
repetitions = 64
mask = mask_grass.tga
thickness = 0.01
}

layer3
{
map = asphalt.tga
repetitions = 32
mask = mask_asphalt.tga
thickness = 0.25
}

Track.tht

Code Select Expand

num_material_layers = 4

material_layer0
{
material = compact soil
}

material_layer1
{
material = soil
thickness = 0.10
}

material_layer2
{
material = sand
mask = mask_sand.tga
thickness = 10
}

material_layer3
{
material = asphalt
mask = mask_asphalt.tga
thickness = 0.25
}


Layer0 is the bottom and each layer after is on top of the previous.

For materials a few of the choices are: compact soil, soil, soft soil, sand, gravel, and asphalt. I think there are 5 or 10 others too.

Hope this helps.

Big Kahuna Dumpster!

Main problem in Beta 4 is when landing;

When landing The front end has a tendency to hit the ground and shoot back up at an extreme rate

When landing on a downhill it's not entirely noticeable

Landing flat it's kinda' noticeable

But when landing near an uphill or on an uphill it's really visible

The bigger the jump and the harder the hit the more it does this

If the bike was under full power and the rider wasn't pushing the front end down when this happened it would seem plausible.
However, even when the motor is at mid-power/idle/shut-off or when the rear brake is fully locked up this still happens


https://www.youtube.com/v/BjnqrQVGqbI

It's kinda' like those mexican lowridin' pimpmobiles with the super powered hydraulic suspension

I'm not entirely sure what's causin' this, but it really kills the flow through an SX style rhythm section

On tracks with higher resolution Heightmaps the ruts blend fairly nicely. Personally I usually set it at about 6 inches per pixel which works out to 0.1524 metres per pixel. The higher the Heightmap resolution the better.

Mace-x

That would make testing camera positions for track making a whole lot smoother.

rc4187