-
Notifications
You must be signed in to change notification settings - Fork 423
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
PoissonRecon.exe terminates due to 0xc000001d Exception #212
Comments
Thanks for the pointer. Given the link, it seems like this is an issue with the project build settings not playing well with hardware. You may want to try to change the floating point model option and see if that resolves the issue. (What kind of CPU are you running this on?) |
Hi, did not work on worked on: This pattern tells me somehow that poissonrecon tends not to run on older cpus. However it puzzles me to see how wide the range is. Ceyhun |
Under "Properties" -> "C/C++" -> "Code Generation" |
Hi there,
first of all, thanks @mkazhdan for the great work.
I have been testing PoissonRecon at different machines and I found out that it terminates with a similar event log on some 3 machines I use. Every one of these machines has 16g ram, and I installed the c++ redist environment.
I tested also several older versions down to 11 and the result was the same.
I use standart horse.txt from the given examples.
Here is the command I use:
PoissonRecon.exe --in "horse.txt" --out "horse.ply" --depth 8 --density --performance --verbose
Here is the output screen:
![image](https://user-images.githubusercontent.com/8968382/147474229-c989aef6-61ad-4bbd-80c3-e5e9ceef4f6b.png)
Here is how the windows event log looks like:
![image](https://user-images.githubusercontent.com/8968382/147473826-5bf3bee7-d377-46a2-a5d3-eedc0f99a26a.png)
Searching for the 0xc000001d I found following:
https://stackoverflow.com/questions/32437899/c-unable-to-start-correctly-0xc000001d-opencv
maybe we are having a similar issue here?
I also tried to run ram check and harddisk check on the machines as it was recommended for 0xc000001d Exception but it did not work out.
Many thanks for your support,
Ceyhun
The text was updated successfully, but these errors were encountered: