We're, i.e. FWGS, dropping old engine support soon once and forever. However, we have new fork based on final Xash3D release and even some unique features, like multiple renderers support. :)
@mittorn works at low memory configuration at this time, that intended to use on ports with <128MB of RAM and once it will be finalized, your changes can be upstreamed.
Only few things are required to be changed:
Cleaner code, you almost don't have problem with this :))
You should agree to maintain your own port. It's not hard, just test global changes and report if other dev has broken something and participate in your port related issues discussion, i.e. bugreports. I recommend you to setup CI for perpetual building and deploying engine updates, so everyone will know which commit has broken 3DS build.
Hi! Congratulations on stabilizing your port. :)
We're, i.e. FWGS, dropping old engine support soon once and forever. However, we have new fork based on final Xash3D release and even some unique features, like multiple renderers support. :)
@mittorn works at low memory configuration at this time, that intended to use on ports with <128MB of RAM and once it will be finalized, your changes can be upstreamed.
Only few things are required to be changed:
If you have questions, ping me here or in our Discord server.