[DRAFT]Rewriting the engine in C++ #7
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
August 18, 2021 17:30
Not using Monogame anymore, switching to C++ DX11/DirectXTK
Made Shader,VertexBuffer, ShaderInputLayout and ResourceCreationException classes. Made Vector4 and Vertex[type]Declaration structs All that code was written in 1 go and it worked for the first time. lmao I'm still amazed
--> I continued to make the code more modular --> Implemented IObject and Camera TODO: --> Implement shader parameters
It looks so broken GAH
Now to fix the axis model...
Kinda works, but all asset previews are broken and save a plain coloured image.
|
CMake building works with VS2022 on Windows 10. Post build processes are broken at the moment. |
Fixed by writing an optimisation in SpriteBatch to not create new VertexBuffers in each Draw() update, but to modify an existing Vertex Buffer with an initial capacity of 1024 and a growth factor of 2. Fixed VertexBuffer usage variable not being used in the ctor. Thus also fixing ::SetData() throwing exceptions. Finally, also fixed the post build process.
|
Currently using a naive font atlas implementation, see results in the picture below: |
Visual Studio doesn't seem to define NDEBUG when switching to Release-x64, this is so fcking stupid. I'm beginning to hate VS2022. May want to try CLion again.
The LookAt vector doesn't seem to update, either way, I fixed some regressions induced by the last refactor
|
For the moment, I will consider the reflection component (without reflecting member functions) and the spritebatch (despite text rendering not being optimised with one single draw call) tasklists complete. I'm switching the goal to a earlier but more unstable release. |
|
Marking #1 as complete, since I won't bother editing the git history. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rewriting the engine in C++ could allow more control and performance compared to the old Monogame releases. Monogame has limited 3D rendering capabilities, namely the assimp implementation allows a maxiumum of 72 bones, BasicEffect (Blinn-Phong with limited control over the variables), broken UVW mapping, and some cross compatibility issues.
I do realise this will take months, but I think it is worth it.
Currently, it is being written using plain Winapi32 and DirectX11 (native windows technologies, duh). Future implementation could use NVRHI and a cross platform GUI library.
Tasks are placed in the order they are finished.
Complete tasks
Tasks that are currently being worked on
TO DO Tasks
Tasks list taken from: https://github.com/orgs/3DRadSpace/projects/10