UnrealEngine VS OpenFrameworks

Visual Studio has a related annoying habit when navigating the call stack (the caller's scope is considered closed if the callee is syntactically its tail) so I wonder whether this workaround would be useful for it as well.

See also this comment in the Unreal Engine code about putting a nop in before as well: https://github.com/EpicGames/UnrealEngine/blob/26677ca1b3c97...

    // Q: Why is there a __nop() before __debugbreak()?

> you can still use it with smart pointers provided by any other library

Is the point of having a kitchen-sink library like this not that you dont have to reach for a 3rdparty library for things that you need 'all the time'?

Certainly, not everyone needs it.

...but, not everyone needs threads either. Not everyone needs an http server; and yet, if you have an application framework that provides them, when you do need them, it saves you reaching for yet-another-dependency.

Was that no the point from the beginning?

unique_ptr is a fundamental primitive for many, as you see from some other frameworks (1), and implementation is not always either a) trivial, or b) as simple as 'just use std::unique_ptr'.

This does seem like a very opinionated decision with reasonably unclear justification.

[1] - eg. https://github.com/EpicGames/UnrealEngine/blob/release/Engin..., https://github.com/electronicarts/EASTL/blob/master/include/...

It is not publicly available. If you click on this link you get a 404 page: https://github.com/EpicGames/UnrealEngine You actually have to go and subscribe, agree to their terms, and then you get to view the source code. It happens to be free, but it is by no means "public".

https://github.com/EpicGames/UnrealEngine/tree/5.2.0-preview-2 For anyone wondering

Like I said before, you have the fixed code here (commit: 23937975).

Before you can access the repository at https://github.com/EpicGames/UnrealEngine, you must: be an Unreal Engine subscriber. have a GitHub account. have associated your GitHub account with your Unreal Engine account as described on the UE4 on GitHub page.

What you need to do is follow this link and diff my file with Epic's file. You can grab settings that I have from mine and plop them into a custom one for yours. Just be mindful if you're developing in VR for what settings you bring over.

Originally it was going to be NetworkPrediction (need to be signed into a github account with Unreal Engine access for that link to work), but since David Ratti left Epic that died and they stopped working on it. (I didn't know it was dead, that was the CMC replacement I was referring to)

Found this while looking through UE commits

Not exactly VJ, but could be used for it. https://openframeworks.cc

Since you have C# experience, take this time to learn more about C++ while you continue to look. While yes, it is very easy to write bad code, it's not a huge deal since you just graduated and are just hacking around. Plus there are a lot of helpers these days to make writing bad code a little less likely.A former mentor of mine gifted me "C++ Without Fear" by Brian Overland which I can recommend. It's not too expensive, I think it was $25 or something like that, likely less used. Also comes in E-book form.If you'd like a gentler introduction to C++, may I recommend openFrameworks?

Have you come across openFrameworks (https://openframeworks.cc/) or Cinder (https://libcinder.org/)?

Not sure it checks all your boxes, but check openFrameworks?

I recently heard of openFrameworks which should make it pretty easy to make your game. It handles putting together a bunch of other libraries and window management so you can focus on drawing some shapes on the screen and handling user input. Sounds like love2d but all C++.

let me know if I can help out - also checkout the forum at openframeworks.cc - the people there are very friendly and helpful - especially with people that are completely new to oF...

I mean, https://www.libcinder.org and https://openframeworks.cc have been mainstays of the creative coding industry for a long time now. A Rust take on the problem shouldn't be too surprising.