search for: missrendering

Displaying 8 results from an estimated 8 matches for "missrendering".

Did you mean: misrendering
2016 Jun 08
1
[Bug 96443] New: Missrendering of Reflections in Talos Principle
https://bugs.freedesktop.org/show_bug.cgi?id=96443 Bug ID: 96443 Summary: Missrendering of Reflections in Talos Principle Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop...
2015 Aug 27
2
gallium state tracker calls calloc for 0 sizes arrays ?
...m) { /* Use fragment program generated from fixed-function state */ } block. Interestingly enough if I allow malloc(0) to proceed from ElectricFence, then the glretrace runs fine, and even renders correctly, where as running the same gl command stream from libreoffice impress leads to missrendering on nv3c. So 2 questions: 1) Is it normal / expected for st_translate_program() to get called with an empty but not NULL proginfo->Parameters resp. num_immediates == 0 ? If not where would I begin to look for finding the culprit of this ? 2) Since the glretrace does work outside of libreoffi...
2015 Aug 27
2
[Mesa-dev] gallium state tracker calls calloc for 0 sizes arrays ?
...;> >> } >> >> block. >> >> Interestingly enough if I allow malloc(0) to proceed from ElectricFence, >> then the glretrace runs fine, and even renders correctly, where as >> running the same gl command stream from libreoffice impress leads >> to missrendering on nv3c. >> >> So 2 questions: >> >> 1) Is it normal / expected for st_translate_program() to get called >> with an empty but not NULL proginfo->Parameters resp. num_immediates == 0 ? >> >> If not where would I begin to look for finding the culprit of th...
2013 Oct 28
3
Trouble on kernel
...feel like debugging, the place to look is > nv30_transfer.c (in mesa). Although I would think this would merely > cause misrendering, not crashes. I'm not going to do that, because I really not that competent for that, even if i know about c programming. I also think that this can cause missrendering, and not crashes, but it also seems that there aren't stored any messages on the crash, maybe it crashes before it can write something to the harddisk? But thank you for your help. Martin
2013 Oct 28
0
Trouble on kernel
...ok is >> nv30_transfer.c (in mesa). Although I would think this would merely >> cause misrendering, not crashes. > > > I'm not going to do that, because I really not that competent for that, even > if i know about c programming. > > I also think that this can cause missrendering, and not crashes, but it also > seems > that there aren't stored any messages on the crash, maybe it crashes before > it can > write something to the harddisk? Well, if compiz/something else *crashes* (i.e. segfault/sigbus/whatever), it's likely there's a log of it. Perhaps...
2013 Oct 28
2
Trouble on kernel
Hi there, Sometimes my computer crashes since i use now ubuntu 13.10 with unity/compiz. dmesg tells me: [ 686.209019] nouveau E[ PBUS][0000:00:0d.0] MMIO write of 0x00000000 FAULT at 0x00b020 and later: [ 1425.565441] nouveau E[ PGRAPH][0000:00:0d.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 1425.565462] nouveau E[ PGRAPH][0000:00:0d.0] ch 3 [0x00056000 compiz[1970]] subc 2
2015 Aug 27
3
[Mesa-dev] gallium state tracker calls calloc for 0 sizes arrays ?
...lock. >>>> >>>> Interestingly enough if I allow malloc(0) to proceed from ElectricFence, >>>> then the glretrace runs fine, and even renders correctly, where as >>>> running the same gl command stream from libreoffice impress leads >>>> to missrendering on nv3c. >>>> >>>> So 2 questions: >>>> >>>> 1) Is it normal / expected for st_translate_program() to get called >>>> with an empty but not NULL proginfo->Parameters resp. num_immediates == 0 >>>> ? >>>> >>...
2017 Jun 11
14
[RFC 0/9] Add precise/invariant semantics to TGSI
Running Tomb Raider on Nouveau I found some flicker caused by ignoring precise modifiers on variables inside Nouveau. This series add precise/invariant handling to TGSI, which can be then used by drivers to disable certain unsafe optimisations which may otherwise alter calculations, which depend on having the same result across shaders. This series fixes this bug in Tomb Raider and one CTS test