Race Track Builder News

New Release Coming Soon with the following features:

v1.5.0.0
- Added: Gizmo for manipulating Objects.
- Added: 64 bit version.
- Added: Support for 8K & 16K textures (in 64 bit only).
- Added: Mask texture can be in different resolution to Main texture.
- Added: Press F5 to reload textures.
- Added: MSAA - Multisample Anti-Aliasing. Improved image in RTB.
- Improved: Increased Speed and reduced Memory usage during creation of Google Map image.
- Improved: AC Terrain Painting speed improved by creating a GPU paint shader rather than a CPU one.
- Fixed: Error when using 3rd party XPacks that hadn't defined Groups for Walls.
- Fixed: Sometimes Texture memory was not being released.
- Fixed: Deleting last instance of an Object would not undo properly.
- Fixed: Adding detailed Terrain to polygons outside the original bounary would cause a crash.
- Fixed: BoundingBox for Terrain Areas were being made higher than needed resulting in unnecessary positive hit-tests.
- Fixed: XPacker Wall Cross-section endcap Material not displayed correctly after Cancel.

Enjoy!

New Release Coming Soon with the following features:

v1.5.0.0
- Added: Gizmo for manipulating Objects.
- Added: 64 bit version.
- Added: Support for 8K & 16K textures (in 64 bit only).
- Added: Mask texture can be in different resolution to Main texture.
- Added: Press F5 to reload textures.
- Added: MSAA - Multisample Anti-Aliasing. Improved image in RTB.
- Improved: Increased Speed and reduced Memory usage during creation of Google Map image.
- Improved: AC Terrain Painting speed improved by creating a GPU paint shader rather than a CPU one.
- Fixed: Error when using 3rd party XPacks that hadn't defined Groups for Walls.
- Fixed: Sometimes Texture memory was not being released.
- Fixed: Deleting last instance of an Object would not undo properly.
- Fixed: Adding detailed Terrain to polygons outside the original bounary would cause a crash.
- Fixed: BoundingBox for Terrain Areas were being made higher than needed resulting in unnecessary positive hit-tests.
- Fixed: XPacker Wall Cross-section endcap Material not displayed correctly after Cancel.

Enjoy!

- Added: Option to export only some components (eg. export Terrain only).
- Added: Option to export components as seperate individual files. This helps where FBX file size was becoming increasingly large.
- Added: New "test" button on settings window for easy testing of Google API functions.
- Added: Failed Google requests will dump error messages to the Log.txt file (run RTB with "\log" parameter - don't include quotes).
- Fixed: Export of Walls would fail for non-AC projects.

Latest release has a bugfix for this problem that only occurred for some users. There are some minor improvements, but nothing radical.

I forgot to make a news announcement for the previous large release. That was Walls. See the video for how that works ...

https://youtu.be/Cssrqpmzx_Y

There are several things I have planned for future releases, although progress on these have been slow. Family commitments, a new job (with long hours and longer commute) have seen my spare time plummet. Programming on a bouncing bus is difficult! So the speed of new releases will be slower, however development has not stopped (as I see some people suggest).

As usual, please use the forums and help each other out with questions. Collectively there are many more people out there with far greater knowledge than just me. ;)

https://www.facebook.com/racetrackbuilder/photos/a.837096909692510.1073741828.806911602711041/1211886562213541/?type=3&theater


Good news! Despite my own advice, I’ve gone ahead and added End Caps to the walls. The old BTB method of clamping down one end using shapes felt out of place in RTB. There’s still more work for me to do before this gets released as the caps add further complexity to the editing of walls and XPacker requires further updates to allow the design of End Caps.

Invisible wall creation has also been added so you can make simpler collision objects for keeping cars from straying from the road. The plan is to eventually extend this feature so String Objects, and even other walls, can auto-generate their own simplified, invisible collision walls – but that will be for a later release.

Hoping to probably maybe possibly be a few weeks away from finishing this release, as there is still much more code to write and bugs to squish.