Forum
Questions, builds, help and the odd argument. The mods and guides are out front.
Fixed it, thanks for making me notice so 😃
Added 1 minute later:
# DHR :
Also why did you remove the noclip camera mode?
Oh so that's why i couldnt go tru the walls anymore lol
Added 32 minutes later:
Hey, are you able, with one of your magic tools, to merge multiple V3 scxes? I'm trying to finish an old map project but the game just doesnt accept more than 345ground meshes and 11 renders(or generally 46 meshes), and i have lost the complete max file so i cant re-export stuff >.<
# Bigg Boss93 :
Btw, i have mixed your Track.java to mines, in case someone still want the camera tilt etc.
I did a similar thing; I basically added all of the lost features back in.
I removed the noclip because if you flip the car the camera goes through the ground which annoys me to no end.
(But its just the camera flag so the line:
cam = new GameRef( map, GameRef.RID_CAMERA, pos.toString() + "," + yTemp.toString() + ",0x02, 1.0,0, 0.01", "external track cam" );
become
cam = new GameRef( map, GameRef.RID_CAMERA, pos.toString() + "," + yTemp.toString() + ",0x13, 1.0,0, 0.01", "external track cam" );
in my version of Track.java
(the first one allows the camera to go through anything))
Added 2 minutes later:
Bigg Boss93 wrote[..]merge multiple V3 scxes?
Probably post them I'll see what I can do (post the .texes aswell than I can merge those aswell).
This is a program that merges scxs in the same directory as the program is.
Try and see if it reindexes the textures properly or not.
LINK
It does partially work, aka, i merged the stuff and it works alright ingame, bar the UV2 and UV3, it only keeps the UV1, do you manage fixing that?
Thanks a lot in advance
Hmm that is strange the data stays there (I mean the UVs) I uploaded a new one try that (LINK) (I changed the handling of the UnkownMapIndices)
Added 31 minutes later:
pre
Added 1 hour 24 minutes later:
I read up on this AA issue: the GPU side MultiSampling (including SuperSampling) needs to be disabled to properly make a depth stencil replacement and get the needed DepthTexture for the depth dependent post-process effects (AO, DoF) so thats that either MultiSampling or AO, DoF and post-process AA this has been the case for a long time so I dont expect it will change in the near future (especially for d3d9).
I see, that's something i didnt know..
Btw, i tried the new tool, same issue as before.
Now i'm not sure if it's not setting the UVS correctly or just using a single self-illumination texture rather than the correct ones, here's a pic(i tried it with the single meshes and they do work right, but once you put them together you get this);
As you can see, both toolbox and lift have effed up shadowmap
Can you give me the textures aswell? It seems I need to test this ingame.
just a question is there a way you can script a trigger in box aspect instead of radial aspect like SLRR does?
It would be really cool for great precision scripting races
BB <3
gorgoil wrote[..]box aspect instead of radial aspect[..]
Can you elaborate on that :/ I dont really know what you mean.
Like a proper finishline?
Well SLRR triggers are done in radial size, which isn't really accurate, sometimes you can miss a sector/finish point because you pass a bit off of the radius of the trigger, but if triggers have a way to script them in a box aspect we can avoid that. I hope I've been more clear
Added 1 minute later:
triggers like garage triggers on valo, because I script races using that way because allows me to create more functional things!
I see, well I see two ways you can implement that for the hackish way you can approximate the box with some smaller triggers with smaller radius (replacing the faces of the box maybe) but this sounds very hackish I would only consider this because multithreading in slrr is very very (very very) dangerous and can easily result in silent crashes,
the other would involve manually checking each like 5 frames (from another script thread) whether the car is in an arbitrary 3D box, your best bet in this case is defining the box in terms of its width height and depth and also two transformations a translation and a YawPitchRoll if you have the box like that you can inverse transform the point(with built in functions Vector3.rotate) you want to check (you will get the point in the boxes space(where the box is centered in (0,0,0) and its rotation is (0,0,0))) and you can use the trivial axisaligned origin centered box case (6 conditionals (whether its x < width/2 && x > -width/2 ... )))
Added 22 minutes later:
That check would look something like this: (I didnt test this thou)
pre
Mind you the point above we give as the position of the box is its center.
Sorry if this has been asked before or if it's not right to ask, but what causes the invalid wear error? I just lost the progress of a 3-hour session of doing night races and progressing through the story and lost it all to that error. Is it known and can I prevent it somehow?