What changed
0 fixes0 additions1 change0 removals
changedThe game is now available as 64-bit (only). The immediate benefit from this is that the "Out of memory" crashes are now fixed. These crashes were occurring usually when starting or ending a battle, or when trying to run the game at 4k resolution. Going 64-bit required large technical changes to get rid of 32-bit only dependencies, but also means that the game no longer depends on outdated and unsupported tech. Replacing XNA with FNA The Microsoft's XNA Framework 4 has been replaced with the FNA library that is an open source reimplementation of XNA. Under the hood the game now uses SDL2, renders using OpenGL instead of DirectX, and installation of the XNA Framework redistributable is no longer needed. FNA also supports Linux and Mac, but porting Battlefleet Engineer to those platforms is not currently planned. Replacing Awesomium with CefSharp Battlefleet Engineer uses a web browser engine to implement the menus and all more complex UI controls. This was previously done through an already discontinued Awesomium library, and is now realized with CefSharp that supports 64-bit applications. Both of these are based on the Chromium web browser, but all the interfacing between the game and the UI had to be redone due to API differences. This was a lot of work, but with the much newer version of Chromium now in use the UI development should be a bit easier going forward.
Battlefleet Engineer changes
changedThe game is now available as 64-bit (only). The immediate benefit from this is that the "Out of memory" crashes are now fixed. These crashes were occurring usually when starting or ending a battle, or when trying to run the game at 4k resolution. Going 64-bit required large technical changes to get rid of 32-bit only dependencies, but also means that the game no longer depends on outdated and unsupported tech. Replacing XNA with FNA The Microsoft's XNA Framework 4 has been replaced with the FNA library that is an open source reimplementation of XNA. Under the hood the game now uses SDL2, renders using OpenGL instead of DirectX, and installation of the XNA Framework redistributable is no longer needed. FNA also supports Linux and Mac, but porting Battlefleet Engineer to those platforms is not currently planned. Replacing Awesomium with CefSharp Battlefleet Engineer uses a web browser engine to implement the menus and all more complex UI controls. This was previously done through an already discontinued Awesomium library, and is now realized with CefSharp that supports 64-bit applications. Both of these are based on the Chromium web browser, but all the interfacing between the game and the UI had to be redone due to API differences. This was a lot of work, but with the much newer version of Chromium now in use the UI development should be a bit easier going forward.
The game is now available as 64-bit (only). The immediate benefit from this is that the "Out of memory" crashes are now fixed. These crashes were occurring usually when starting or ending a battle, or when trying to run the game at 4k resolution. Going 64-bit required large technical changes to get rid of 32-bit only dependencies, but also means that the game no longer depends on outdated and unsupported tech. Replacing XNA with FNA The Microsoft's XNA Framework 4 has been replaced with the FNA library that is an open source reimplementation of XNA. Under the hood the game now uses SDL2, renders using OpenGL instead of DirectX, and installation of the XNA Framework redistributable is no longer needed. FNA also supports Linux and Mac, but porting Battlefleet Engineer to those platforms is not currently planned. Replacing Awesomium with CefSharp Battlefleet Engineer uses a web browser engine to implement the menus and all more complex UI controls. This was previously done through an already discontinued Awesomium library, and is now realized with CefSharp that supports 64-bit applications. Both of these are based on the Chromium web browser, but all the interfacing between the game and the UI had to be redone due to API differences. This was a lot of work, but with the much newer version of Chromium now in use the UI development should be a bit easier going forward.
