Neon unreported bugs (i think)

1. Sometimes i render some scenes with the back faces culled in the neon viewport.

Although when i try to have also the ground plane present in the scene, it results as if it was flipped (when the camera location is positive in Z the plane is invisible and)

2. when i capture the screen shot with _ViewCaptureToFile and choose .png format with transparent background the result is an overexposed-semitransparent (useless) image.

same thing when you forget to untick the "transparent background" saving in .jpg

You get the same overexposed image with no transparency this time (of course)

3. sometimes when the Neon render passages finish, I get a result the same overexposed image as discribed above (actually it looks like the initial phase when Neon is in the "starting" mode before calculating)

4. when i capture the screen shot in different resolutions with _-ViewCaptureToFile it works but, there's a strange behaviour of the system.

Half of the screen becomes black although Neon works and tryies to reach the passages that were present in the moment of the command launch

also, but this is not a bug, there's no indication on the real progress of the render (it just shows you the % progress of each neon passage but not how many are left)

Enough with the bugs now just some questions:

1. Is there any probability that the emmision color option in rhino material can actually act as a lighting source?

2. is there ansy possibility in the near future ti get OpenCL/CUDA support? or shall i just get a Caustic Board ??? :-)