datarealms / ccoss Goto Github PK

It is safe ?

It's been a while, but there was, at one point, a Linux build.
Are build instructions for that still around?

I propose to change the license of the project from AGPL3 to AGPL3+
Reasoning.

Hey,

as the title mentions, I'd love access to the files from the beta branch, which I don't seem to be able to get to, from a Linux machine.

I'd like to use it to verify that it is, or isn't the reason the game crashes, when m_pCraftCollectionBox is null, when accessed at Menus/BuyMenuGUI.cpp:262

Add Steam support through Steam shim

The game then interacts with Steam through a prebuilt (closed source) child process.

It only supports stats and achievements.

No game data and most of required runtime DLLs are included, you should get those from the Cortex Command beta branch on Steam.

Any info on how to get the beta branch? There is no beta branch selectable and no code to unlock it anywhere.

While in fullscreen, if the user is using Windows' scaling settings to increase the size of the desktop, Cortex Command will also scale along with it, causing content to be cut off of the screen. I'm running the ccoss beta straight from Steam unmodified.

Without scaling:

With scaling:

Playing with a 1920x1080 desktop resolution at 125% scaling.

I have CC on Steam, and was excited when I saw that there was an open source release. I don't have the whole toolchain set up on Windows, though. I had hoped to find a release, but the tab is empty. Is it in a fit state to make a user-facing build available?

cling based C++ as scripting language / hot code reload
Why? Able to run C++ script in runtime or compile it for max speed ( as in example https://github.com/derofim/cling-cmake )

HOT code reload
possible approaches:

store app state
fix cling undo for files
https://root-forum.cern.ch/t/loading-unloading-class-as-interpreted-macro-in-cling-multiple-times/32976/2

execute cling code to change callbacks & variables
nested cling::Interpreter with multiple cling::MetaProcessor
IDK how to do it, but you can create child cling::Interpreter