I noticed that 3Drad space uses C# and monogame. but I suggest that it should use OpenTK as it is better.
https://opentk.net/

Old news, I'm rewriting 3DRadSpace using plain DirectX and C++ 20

Current 0.1.0a fork here : https://github.com/NicusorN5/3D_Rad_Space

I think you should use OpenGL as it is Cross-Platform. or go with OGRE (https://www.ogre3d.org/) as its support both OpenGL and DirectX. (https://www.ogre3d.org/about/features)

I will use Vulkan as GAPI when writing 3DRadSpace for Linux, and I don't think OGRE is meant for writing game engines.

It's not a game engine, it's a rendering engine (Object-Oriented Graphics Rendering Engine) and there are games made using OGRE for example Kenshi. and for physics you could use OgreODE which is a physics wrapper for OGRE.

I corrected my post.

One minute of Googling reveals game engines based on Ogre (for example, NeoAxis).

Anyway, one goal of 3DRadSpace is using as less layers of abstraction as possible, because low-code/no-code applications tend to have specific limitations and performance quirks. This is why I decided to use low level APIs like the Windows32 API (Windows.h) and DirectX11.

I just noticed that higher level applications, and application development environments tend to have lower performance. Examples include : Python (CPython is a improvment, but Python applications can be 10x+ times slower than programs written in Rust or C), 3D Rad v722 itself (The issue with 3D Rad v722 is the exposed scripting API - it is too limited : you'll have to reverse engineer and hack the original 3D Rad to obtain the most performance of it), Pika Software Builder (the performance is decent, but v4 was limited, and v5 is buggy . The company that made PSB is now bankrupt.), Clickteam Fusion (I played games that can't handle 2k+ objects even on my AMD Ryzen 7 laptop).

I intend 3DRadSpace to allow both low-level and high level coding (think about Unreal Engine), to avoid as much as possible the performance issues caused by the nature of low-code environments.

I kinda understand what you mean, but what do you mean by allowing both low-level and high-level coding?

Have you seen how Unreal Engine implements both Blueprints and low level programming by exposing a C++ API?

I think I remember that UE also had Lua, but it was removed because limitations and trouble showed up (?)

Oh okay, so your gonna add a visual scripting language?

Yes, I have that in mind.

Also, which programming language will be the main programming language in 3DRadSpace?

C#? I also want to implement support for more languages (like LUA, or Python)

I don't think C# is a good idea. as alot of people would be like "Why should I go with this instead of Unity or Godot?" i suggest to go with AngelScript or even Rust or make your own Programming language.

Notice the question mark. I was initially thinking about C++ when I started writing 0.1.0a, but it may be too complex?

Rust sounds kinda cool ngl

JavaScript is more easier so it I think its better to go with JavaScript

JS? Honestly ew, I'd rather use Python anytime

For me I'd rather any programming language with BASIC syntax, as I installed almost all BASIC languages.

...go with angelscript: at least it will somehow give a nod to 3drad, and the 3 or so existing users won't have to learn a new language :-P

or you could use this 3drad-like engine in c++ with vc2017 compiler instead:

'You can create your own game engines based on Titan, however they must clearly state that they're "based on Titan Engine" with the name linking to: https://esenthel.com or https://github.com/Esenthel/EsenthelEngine and 15% of income generated from your engine and engine related services (including but not limited to: donations, license sales, adding features, providing support) must be shared with Titan Engine creator.'

I think that Angelscript and C++ should be the main programming languages then C#.

Also which version of DirectX?

I'm using DX11. Support for DX12 and Vulkan is also planned, but that's not a goal right now.

2 now cause i'm moving slowly to unity.

I should add, i will still use 3drad for quick prototyping and testing models.

so now there are 2 left...

3drad's scripting is not an issue for me. it's making model/texture assets, physics/AI and shaders/lighting that is the time killer, unity does not make those any easier [unless you use pre-made assets of which unity has many, and is a recipe for failed asset flips, 3drad does not have that option, so forces you to be original]