(Note, you will need to use this download link rather than the auto-update feature, as 1.9.2 will not update to an unstable version, only the next stable version)
https://downloads.kronosaur.com/TranscendenceNext.zip
This version introduces:
- 60 FPS gameplay
- API 54, focusing primarily on new engine features and bugfixes
- new projectile & fragment options
- the ability to make shields that use consumables (like the superconducting shield) and have the AI actually use them properly
- the ability to restock shipbrokers and ensure they have more options for sale
- fixes for projectiles using API53 and older code
- fixes for autodefensedevices being too slow to acquire new targets, resulting in them mostly missing
Bug fixes: (George to post the link once it is updated on ministry)
API 54: (George to post the link once it is updated on ministry)
TransData 3.5.0: (George to post the link once it is updated)
Known issues & upcoming changes:
Crashes:
- Application of drag forces on wrecks (to prevent them from drifting infinitely) is sometimes causing a crash. Mostly commonly observed on the intro screen. - Under investigation
- Projectiles will sometimes detonate away from their actual location. Detonation may also be extremely premature - Fixed in Alpha 2
- Single fragments with tracking will be jittered away from their intended direction of travel - Fixed in Alpha 2
- Setting some values to "0" in XML that accept diceroll or range notation (ex, 1-10 or 2d6+4) result in defaults being inappropriately applied instead of being treated as "0" - Under Investigation
- Projectiles with tracking still seem to start travel at the wrong angle - Under investigation
- Some stuff animates really fast (cosmetic bug only, due to 60FPS) - Under Investigation, Fix planned for a later release
- (objDestroy obj) was deprecated in API54 (Replacement is (objRemove obj)) - however, the deprecation message is overriding the object actually being deleted - Wont fix, but moving forwards there will be fewer 'breaking-changes-on-new-APIs' (unlike the ShipType Hull update)
- In the note of the above issue, the original default behavior for fragmentation is reverting to "trigger", HOWEVER it is recommended you put the following parameter into all of your API54 fragments to get the Expected behavior:
Code: Select all
fragmentAngleDirection="direction"
- The S3 and TM7 are still overly strong due to all fragments hitting one segment and bypassing most point defense systems. - Under investigation, may require Alpha 2 to be released first before they can be fixed.
- Compatibility UNIDs library specified rsMolotokHD as the replacement for... rsMolotokHD. (The correct replacement is rsMolotokB - Fixed in Alpha 2)