Jpez1432 wrote: Sat May 23, 2026 9:00 am
Hey KMaster, not sure how you do the scaling in your rendering. I use OpenGL so everything is normalized. I multiple/scale the models by 1/65536.0f, swap x/z and negate z. the scrape points and wheel positions and axlebar/driveshaftpos I scale all by 1/32.0f and then the fourlinks are the absolute value of the the axlebars and the shock position is the wheel position * 0.256f x. kinda hard to explain if you want I can send some code or try and explain better.
Question: Where did you get those values? because mine are read directly from the BIN file header, the file tells you its own scale factor.
magnify power block type was something I discovered while working in JTraxx since it wasn't specified anywhere, at least not openly. I got some help from Striker (the dev of Terminal Fury) since I was having some issues with hellbender model scaling and found out about it. it wasn't even specified in the jtrfp library or Traxx source.
here's a complete AI agent code analysis:
Code: Select all
Each vertex component is a raw int32. The least significant bit is a geometry flag, not part of the coordinate, shift
it out first:
coordinate = rawInt32 >> 1
Then scale using magnifyPower, a value stored directly in the BIN file header (block type 0x14):
scaled = coordinate * (512.0 / magnifyPower)
The file is self-describing: magnifyPower is literally the second int32 in the file. It's almost always 65536, which
simplifies to coordinate / 128, but reading it from the file is the correct approach. Hardcoding 65536 will silently
produce wrong geometry for any BIN that uses a different value.
Skipping the >> 1 or using integer math instead of float will also break geometry.
Regarding TRK positions (wheel anchors, scrape points, axlebarOffset, driveshaftPos):
These are already in game units, no scaling needed. They are used as-is alongside the BIN-scaled vertices.
On the fourlinks and shock:
Fourlinks = abs(axlebarOffset) confirms the X component is a half-width magnitude, not a signed
lateral offset. The shock_x = wheel_x * 0.256 is good to have for suspension visualization.
if you need more info on it let me know
Fila wrote: Sun May 24, 2026 5:11 pm
Also... for some reason after downloading the latest version the axle bar won't show up anymore (and lights are not working).
I "hard reload" and erased all cache data after deploying the new version. In chrome: Dev tools enabled > right click reload button > empty cache & hard reload. Otherwise it will fail to load.
Fila wrote: Sun May 24, 2026 4:53 pm
So the way the truck looks in the JViewer is the default position when the truck is in the air. In the game it doesn't look as odd because of the additional drive shaft and fake struts giving you the illusion it is all connected. Once it lands on the ground, it has a different "resting" position that I will have to look and see if I can find it. It's probably a fixed value for all the trucks since the game doesn't take into consideration weight etc.
Good info, then in the meantime I can just squash the truck a little bit to make it look more familiar.
