-
Notifications
You must be signed in to change notification settings - Fork 435
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
Failing to run examples #7
Comments
Hi. The reason why you get compilation error is simply because I made lots of breaking changes in the API and only kept the teapot example up-to-date! Also you get an error in the teapot example because it expects the SDK to be installed on the machine. I just pushed a change (69d6b90) that should fix that. |
because drivers are drivers and SDKs are SDKs why would I need the lunar SDK to run/compile vulkano? anyway I downloaded and installed latest https://vulkan.lunarg.com Updated master to 69d6b90 and get this error (after second run to dismiss extra compiler warnings)
Here is vulkaninfo if of any help |
You shouldn't need to install the SDK. The change I pushed fixed the example so that it no longer requires it. For your other problem, that's interesting. The instance doesn't support |
This should be fixed by 3e15fd3. My AMD driver is probably faulty. |
Nice, but does that part need to be static and not dynamic? Anyway, now I see a creation of a window... but still
And thanks for your fast answers :). |
Please provide a backtrace with |
Here it is
|
By the way, I try the same with image example (set RUST_BACKTRACE=1), but stack trace doesnt show
The example uses swap chain so, the VS debugger catch this And finally |
Commit 7ab8067 should fix the teapot issue. As for the swapchain, could you tell what error Visual Studio reported for the crash? |
I updated to latest 31415af and the teapot example now launch on exit the VS debugger instead of show the backtrace... This is what I get in the output log... from VS...
The command promt only show
Sorry I cant help more, but this are the windows I get Later it prompts to choose a debugger On the left on the bkreaced at exception if I click go to source I get But if I go to thread 1 and click on the only call of teapot I go to |
Teapot sample is broken for me again,
I'm currently trying to write my first vulkano program, but that unfortunately breaks it |
@auruss It compiles fine for me, plus the framebuffer code is a code that I haven't touched in the last few days. Make sure you have a recent version of Rust. Other than that, I strongly encourage you not to use vulkano right now. Like the readme says, its API breaks every 5 minutes. |
@tomaka I wonder what your configuration is (OS, rust version, Hardware and maybe drivers probably could be shared on the read me in the mean time vulkano become usable on any config). |
@tyoc213 Windows and AMD drivers should work. |
I see, guess I will need to build a little computer with and R9 fury or something. By the way, I can confirm the compile error above.. Thought dont know why it compiles in your end and not on us, Im using The problem did come from the merge of tomaka/vulkano/pull/9 specially 556adf8 (Render pass is now a trait) parent commit did compile teapot. |
I investigated a bit, and apparently the Clone trait is only available on IntoIter starting from Rust 1.8. |
Well, 1.8 comes in April, so I uninstalled 1.7, installed https://www.rust-lang.org/downloads.html 1.8 (which is beta now, 1.9 is nightly) and under A red teapot! Well I jus tracked that the teapot example did start running in this commit b7fb160 |
Since Rust 1.8 is now stable and a warning has been put in the README, I'm going to close this. |
Hi there, I have Windows Insider with 364.51 NVIDIA Drivers. and Im using rust 1.7 mscv from https://static.rust-lang.org/dist/rust-1.7.0-x86_64-pc-windows-msvc.msi and with VS2015 community.
Do I need nightly or something? I dont think because
cargo build
ends with a lot of warnings but 0 errors.And I get
And
And here is a different one
And
The text was updated successfully, but these errors were encountered: