It doesn't have to be this way.
@rfleury24 B takipçi
23.341 görüntüleme
10 Yorum
Yorumlar X (Twitter) üzerindeki orijinal gönderiden alınmıştır

@JohnBurton
I made a little c++ test program to try out raddbg, and I'm finding it often takes 1-2 seconds to step to next line. This is slower than I would expect although obviously much better than the 10 seconds mentioned. Is this expected, or is something not working as expected? Or I didn't do something right? (Not a complaint or anything, it's a great program, I'm just finding it slower than I might have expected?)
5 beğeni

@ryanjfleury
It should be instant. Can you send me the program’s EXE, PDB, and source?
4 beğeni

@_quietwarrior
*eagerly awaits macOS support*
3 beğeni

@birch_js
How does this fare on a medium-sized React Native iOS app when debugging Objective-C code?
3 beğeni

@ryanjfleury
Haven’t tried it, as we do not support MacOS yet, but even with codebases like Unreal Engine (1000s of DLLs, many millions of lines of code), stepping is ~instant. There are basically no reasons that it should take anything more, in common cases.
3 beğeni

@rasulseidagul
Poor people… they have never seen good.
1 beğeni

@stanlyhalo
What rendering API are you using? The resizing is so smooth compared to modern APIs that requires swapchains. And are each "element" being rendered one at a time, or is it watched on the gpu? If so are you doing style interpolation on the gpu? What about buffer updates?
1 beğeni

@ryanjfleury
It's a custom renderer, on Windows it uses D3D11 as a backend.
2 beğeni

@codewithimanshu
Progress requires change.

@X1nto
Lowkey the only good thing to ever come out of (an) Epic Games (employee). @TimSweeneyEpic put him in charge of EGS.
