Hello folks,

I keep opening OS_Sapien, and... well, let's just say things don't run properly. I think I've pinpointed it based on memory, since some maps run fine with other programs open (but if theres too much, then it gets hiccupy, but by "open stuff", im refering to simply google chrome, dropbox, notepad ++ and maybe guerilla, maybe steam, and skype). I keep getting this annoying message in my Sector 09 scenario that keeps popping up (similar to how the "incompatible bitmap in shader error" pops up whenever you look at that particular object that produces this error (im sure you know what i'm talking about)), but it basically goes like this:

10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed
10.21.15 23:14:41 \halopc\haloce\source\rasterizer\dx9\rasterizer_dx9_widgets.c(959): D3DERR_DEVICELOST in hr (code=-2005530520, error=<can't get description>)
10.21.15 23:14:41 ### ERROR rasterizer_widget_get_occlusion_test_result failed


I was wondering if anyone has any background with this error, and what could be causing it. Thanks for your reply in advance :D

IIRC this is caused by other programs using DX9 while Sapien is starting/running.

Try only using actual 2d textures in your shaders, so no interface or sprite. (If you are using interface because it doesn't have mipmaps just set the mipmap count to 0 in the texture.


This is caused by Sapien not getting access to your graphics card. If you don't want this, then don't alt-tab from Sapien. It is completely harmless so Idk why this is actually a complaint.

Thank you for your response, mike. The incompatable bitmap was just an example to how this error behaves, but I will look into that if it ever happens again. I figured out that it was the tags that I was using, and their bitmap resolutions was eating my scenario's limits very quickly. I removed them all from my scenario and scenario's globals, and that fixed the issue. Thank you for your responses guys!!

This can be caused by steam application as well. I have this issue before few times and I only need to reboot steam to resolve it. Just a helpful tip in case you run into this again in future.