Closed GoogleCodeExporter closed 9 years ago
Hi.
Actually you're in luck (sort of), there is an undocumented command line option
--ffp (fixed function pipeline) that does that.
Could you post some screenshots of the text rendering issues you're seeing?
Ideally if you pause it and take some screenshots with P toggled on and off
(you can take TGA screenshots with F12).
Also what video card do you have?
Cheers
Andrew
Original comment by acaudw...@gmail.com
on 28 Nov 2011 at 11:02
Great, the --ffp option workaround works.
Attached are the screenshots you requested. The 'default' is as it starts (not
using the --ffp option of course); after pressing 'p' it turns into 'afterp'.
I'm using a laptop with Intel HD graphics.
Original comment by loicwout...@gmail.com
on 28 Nov 2011 at 12:55
Attachments:
Original comment by acaudw...@gmail.com
on 28 Nov 2011 at 8:30
It looks like it's a divide by zero error in my shader code. oops.
Original comment by acaudw...@gmail.com
on 28 Nov 2011 at 8:48
Have just fixed this in the development version, will be in the 0.38 release.
Original comment by acaudw...@gmail.com
on 28 Nov 2011 at 9:03
Original comment by acaudw...@gmail.com
on 21 Apr 2012 at 8:38
Original issue reported on code.google.com by
loicwout...@gmail.com
on 28 Nov 2011 at 10:37