Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide C++ code link just before "Frames in flight" #150

Open
buzmeg opened this issue Sep 27, 2019 · 3 comments
Open

Provide C++ code link just before "Frames in flight" #150

buzmeg opened this issue Sep 27, 2019 · 3 comments

Comments

@buzmeg
Copy link

@buzmeg buzmeg commented Sep 27, 2019

Could someone please create a C++ code link just before the "Frames in flight" section? ("Drawing a triangle"->"Drawing"->"Rendering and Presentation"--https://vulkan-tutorial.com/Drawing_a_triangle/Drawing/Rendering_and_presentation)

If you don't get a triangle, it's REALLY hard to find the error as there is no code to compare to at that exact point--you can only compare to the code that adds a whole bunch of extraneous "frames in flight" stuff. Providing a C++ code link right before that point would make life a lot easier on people.

It sure would have helped me. I had to basically restart from ground zero a second time and walk forward to find my error. :( I had two bugs simultaneously and I couldn't extract one from the other because I didn't have a good basis for comparison.

Thanks.

@chenzhekl
Copy link

@chenzhekl chenzhekl commented Nov 29, 2019

How about uploading your code for others to check? Besides, it might be better to ask this question in the Disqus comment, I guess, since it's not an issue of the tutorial itself.

@Overv
Copy link
Owner

@Overv Overv commented Nov 30, 2019

Could you elaborate on which bugs you had?

@buzmeg
Copy link
Author

@buzmeg buzmeg commented Dec 3, 2019

There was a driver bug (in MoltenVK) and an allocation ordering bug (my fault) which would cause my driver to crash out. However, fixing one without fixing the other looked the same from a crash point of view. Until I redid all my code from the ground up and fixed the allocation ordering bug, it was absolutely impossible to pin down the driver bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.