KartmakerGUI 1.0.3

[SpringEThing]

SpringEThing submitted a new resource:

KartmakerGUI - Sprites to WAD with a helping hand

Introduction
Kartmaker is a fantastic and invaluable command-line tool for the SRB2Kart modding community which allows one to automatically assemble a WAD representing a character for SRB2Kart in as simple as a click and a drag of a directory onto the Kartmaker tool's executable. The tool itself is programmed in C and being so close to direct memory manipulation one can imagine that it's blazing fast. For veterans, nothing will replace Kartmaker for simple character WADs. Whilst the...

Read more about this resource...

 

[cozyraf]

SpringEThing submitted a new resource:

KartmakerGUI - Sprites to WAD with a helping hand



Read more about this resource...

Pretty great to use for organising a bit, welcome to releases!

 

[SpringEThing]

SpringEThing updated KartmakerGUI with a new update entry:

Last-Minute Post-Launch Change

- Removed the warning boxes that appear when one clicks an elipses button to open a file explorer dialog but then chooses to cancel out of that dialog, seems like overkill to me.

Read the rest of this update entry...

 

[SpringEThing]

SpringEThing updated KartmakerGUI with a new update entry:

A Flippin' Slip-Up

~ The 'flip' optional boolean parameter for each frame defined in a Kartmaker template was previously misinterpreted during the WAD generation process to have contradictory behaviour to the original Kartmaker software. This has now been resolved. Special thanks for Discord user Spazcakes for bringing this major issue to my attention!
+ Added the 'simpleflip' optional boolean parameter for each frame defined in a Kartmaker template. This boolean (which cannot be set to true at the same time...

Read the rest of this update entry...

 

[ssngreenscreen]

Imagine there is a srb2 version

 

[decending coffee]

does this work on ring racers?

 

[SpringEThing]

SpringEThing updated KartmakerGUI with a new update entry:

Watch Out! Oil Leak!

~ Fixed an IDisposable not being disposed of, previously potentially leading to a memory leak. This was extremely unlikely to be a serious problem for any user as first of all the virtual machine that all C# code runs in has good enough GC that eventually the IDisposable memory would die and second of all the leak in particular would take hours of using the program constantly doing one thing in particular over and over to affect the average PC

Read the rest of this update entry...