0.4.1

[hogsy]

A smaller release today aiming to fix some issues. I've not had as much time (or motivation) as I'd like, hence the smaller release.

Of note is a /legacy command-line argument that's been introduced which allows you to use the original leaked BF and retain the fur behavior from that version (mostly). Though I would still recommend using Droolie's patched BF as that'll obviously give you a more stable foundation and exclude you from having to use that argument 😉

Leaked BF in Jaded without /legacy.

Leaked BF in Jaded with /legacy.

Changes

• Added '/legacy' argument which can be used if you're loading the original leaked BF (Allow us to use the original leaked BF with working fur #62)
• Fixed memory alloc error message displaying requested block size incorrectly (bc4cdc1)
• Fixed crash on script error caused by an invalid object (4283de4)
• Fixed crash when spawning into a level with BGE water (40a2f02)
• Fixed a few possible collision related issues (ebb6866) (Droolie)
• Removed crash reporting utility due to abuse

Known Issues

Jaded is still a work-in-progress, and unfortunately being human with a full-time job means I don't have as much time to dedicate to the project as I'd like. This means that there are still a few issues that I've not had the time to get round to (besides things that already have tickets raised for them).

• There is some input latency in the editor when the draw in the 3D viewport is taking too long. This is hampered further by unnecessary refresh calls resulting in the editor drawing multiple times on input. This is an issue that's been there since the original leak, and it's been improved but there's still further work to go here.
• The debug build has RTC enabled now which will pick up on instances where variables are being used without being initialised, which was responsible for some odd behavior. I've tried to fix as many of these as I can but there will still likely be many I've not yet caught. Let me know if you see any errors returned in relation to this, and I'll look into it.
• Script errors/warnings are ignored in the release build. If you're doing any work on scripts and need to see these, you'll need to use the debug build for now. This will be resolved in the next release.

---

This discussion was created from the release 0.4.1.