Full notes
Full Foresight update
Read the full published notes in a cleaner layout. The original post stays linked below.
What changed
- Compatibility
- Gameplay
- Fixes
- Performance
Dear all, As promised, Foresight 1.3 has been released!
What's new?
The main font resolution has been upgraded. Just, see it for yourself to see the difference. - You can now V-sync while being in windowed mode. - Change of engine version from 1.0 to 1.2. StridesLib Engine v1.0 was built based on the much older VS2005 runtimes. However, in v1.2, it's built on the more recent VS2015 runtimes. Thus, for backward compatibility's sake, both runtimes will be installed on your machine. StridesLib Engine v1.2 did resolve a lot of stability issues. However, Foresight might not have fully be compliant to it yet.
Adjustments
There was a feedback long ago that Foresight looked like a white saturated mess in heavy battles. After that, we went into observing popular space battle scenes like TCW to understand how best to represent explosions without over saturating things. As such, we've modified certain effects to be blended as-per-normal... in a way, it might feel a little weird but it does show both texture and depth rather than saturation. Of course, some things will still cause a mini-sun, ie, combined nuclear explosions. But that'll be the only case. Hope the new slightly adjusted look and feel will be well-received.
Bug Fixes
Fixed a bug where ships die but aren't removed from the game - Fixed a bug when you try to insert characters into your chat and it glitches - Fixed a bug where "Load Game" in the main menu doesn't show anything - Fixed a bug where the game - on first startup, doesn't start up properly - the symptoms are in scenes where there're distortions, the game is rendered twice, once with 1/4 top-left and the other, a complete scene. - Fixed a bug where Campaign 3, Mission 3 (Mission 23) cannot be completed because the Vindiator will get stuck at Phobos.
Caution
It does seem that Foresight might crash when you close it. This could be due to some difference with the order of release. Therefore, you might still encounter crashed when you close Foresight. - Due to the complexity of the crash, which only occurs during release, it'll take some time to find out the cause.
Conclusion
Some friends initially discouraged me from working on this patch since the game is already 4 years old. However, I personally feel that if the playing experience is severely impeded, I'll need to take responsibility and fix it. Surely, that's what I feel when I encounter a game that has logic-breaking, stopper or crash bugs. I'd also like to thank all who posted feedback on bugs and improvements. You will always be listened to and we'll try to improve as much as we can. (realistically, we can't fulfill everybody's wishes :( ) Thanks for supporting Foresight and have a great weekend! Regards, Jeremy
Source
Changelog.gg summarizes and formats this update. How we read updates.
