search

pbfy0 / visvis

Automatically exported from code.google.com/p/visvis
Other
0 stars 0 forks source link

Problem with volume rendering #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
After executing the volume rendering example from the wiki, I get:

---
In [27]: t = vv.volshow(vol)

In [28]: Warning in shading code: Fragment shader was successfully compiled to 
run on hardware.
Warning in shading code: Vertex shader was successfully compiled to run on 
hardware.

Aborted

---

Do you know what is happening here? Is it related to my graphics card drivers 
probably? I am on Ubuntu 10.04.

Thanks.

Original issue reported on code.google.com by uni.desi...@gmail.com on 4 Jul 2010 at 1:58

GoogleCodeExporter commented 9 years ago 
It seems as if there is not really an error, but merely some info. 

Could you please test this for me and change line 304 of textures.py to say 
"return True"?

Original comment by almar.klein@gmail.com on 4 Jul 2010 at 9:27

GoogleCodeExporter commented 9 years ago 
I did the change in textures.py, but still the same.

It displays the window I attach when running the example code. There seems
to be another problem, because the bars are not shown.

If I call In [27]: t = vv.volshow(vol) a second time, it Aborts.

Any ideas?

Original comment by uni.desi...@gmail.com on 5 Jul 2010 at 8:10

Attachments:

GoogleCodeExporter commented 9 years ago 
Doh! I should have said:
Change line 302 to say "return False". 
Could you try again please? Sorry for that :)

Which bars do you mean are not shown?

Original comment by almar.klein@gmail.com on 5 Jul 2010 at 9:24

GoogleCodeExporter commented 9 years ago 
Great! I tested and it works now without aborting. The information message is 
still shown. And I also see now the bars,. By bars, I meant
vol[50:70,80:90, 10:100] = 0.2
vol[50:70,10:100,80:90] = 0.5
vol[10:100,50:70,80:90] = 1

Thanks again.

Original comment by uni.desi...@gmail.com on 5 Jul 2010 at 9:38

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 02134ee993.

Original comment by almar.klein@gmail.com on 6 Jul 2010 at 8:26

GoogleCodeExporter commented 9 years ago 
Great, I changed the source to check for errors in a better way and only print 
the info log if there's an error.

Original comment by almar.klein@gmail.com on 6 Jul 2010 at 8:30