rendering problems on IRIS gpu

[haraldsteinlechner]

currently there seem to be rendering problems on intel iris hardware. We have a repro on a project member's computer. After writing artificial rendering tests which all worked pro3d has now support to set render control properties such as multisampling count and mapping etc.

The attempt can be found here: 844d257

[haraldsteinlechner]

our test build: http://download.vrvis.at/acquisition/pro3d/iris-test.zip

[haraldsteinlechner]

Thanks to Kens testing sessions we could pin the problem down to a problem with multisampled rendertargets. The current workaround for iris integrated graphics is currently to set samples to 1.
The problem is still under investigation @hyazinthh @ChristianLuksch since it is not clear whether this is a driver bug or a subtile spec violation on our side.

The current plan is:

• officially support setting multisample count from outside. this is done in the branch mentioned above and will be merged for the next release
• mention problem in 'troubleshooting' page which can be included in manual and on github
• In the meanwhile we are trying to find out if driver bug or aardvark bug ;)

[ThomasOrtner]

the damn coordinate cross :D

[haraldsteinlechner]

@hyazinthh do you know the status of this in the base libraries? should be fixed right? if so we could remove the workaround

PRo3D/src/PRo3D.Viewer/Program.fs

Line 201 in b145dfc

if runtime.Context.Driver.renderer.Contains("Intel(R) Iris(R) Xe Graphics") then

[hyazinthh]

I don't think so: aardvark-platform/aardvark.rendering#86

[haraldsteinlechner]

don't think so means - no not fixed, keep workaround, right?

[hyazinthh]

Yes, that's what your final comment on that issue suggests at least.