On Wed, Feb 3, 2010 at 12:33 AM, John Denker j...@av8n.com wrote:
The rc4 from a couple of days ago has a glitch
that I haven't seen before:
FRAGMENT glCompileShader FAILED
FRAGMENT Shader infolog:
Fragment shader failed to compile with the following errors:
ERROR: 0:28: error(#162)
On 02/03/2010 12:22 AM, Tim Moore wrote:
This might be associated with the replay system, and I don't see a good way
to turn it off completely. Try starting with /sim/replay/disable set to true
and see if that changes anything.
No change.
Also FWIW turning off random vegetation = no change.
John Denker wrote:
The commit messages for these commits seem self-explanatory.
commit f38db3f433e77cd59c2332dbda779774768bcf96
Author: John Denker j...@av8n.com
Date: Tue Feb 2 22:00:17 2010 -0700
Get rid of annoying Failed to load object message.
diff --git a/materials.xml
On Wed, Feb 3, 2010 at 9:09 AM, Tim Moore timoor...@gmail.com wrote:
On Wed, Feb 3, 2010 at 12:33 AM, John Denker j...@av8n.com wrote:
The rc4 from a couple of days ago has a glitch
that I haven't seen before:
FRAGMENT glCompileShader FAILED
FRAGMENT Shader infolog:
Fragment shader
( not sure how to reply to the thread, I don't have it in my mail.
This is in reference to :
http://sourceforge.net/mailarchive/message.php?msg_name=4B58FCDF.1000905%40daffodil.uk.com
)
Hello,
I have been looking into the 787 yasim fuselage , using the blender
import script by Melchior Franz
Hello,
I have been looking into the 787 yasim fuselage , using the blender
import script by Melchior Franz as suggested.
Using the original 787.xml file as it is in CVS now, ie :
fuselage ax=-13.6 ay=0 az=1.4 bx=-13.6 by=0.00 bz=1.4
width=5.9 taper=0.1 midpoint=0/
we see the
On 02/03/2010 01:37 AM, Tim Moore wrote:
What hardware and driver? A possible workaround is to comment out the
conditional tests related to gl_FrontFacing
in Shaders/default.frag and Shaders/mat-anim.frag.
Tim
Whoops, never mind. Try the Shaders/mat-anim.frag that I just checked into
CVS
On 02/03/2010 02:00 AM, Tim Moore wrote:
Do you still get it now, after the shader errors have
(hopefully) been banished?
Three answers:
1) The shader issue is greatly improved. No more nasty
shader-related error messages on the console. This is
an improvement at all airports, not just
Hi,
I mention this because I betcha lots of users of
the new release will not have hardware that can
handle this. I've got a rather capable machine,
capable of 70 frames per second of normal
scenery, but it can only do 20 in the NYC area.
An it is an ugly 20. Very jerky. It
Hi,
I tested pre3 on my two macs.
Dual core 27 iMac report: As previously fg won't work on my iMac. As
with the previous pre-releases fg crashes during initialization. I am
working on getting a debug compile of Tats code. I've reached the end of
compiling all the packages but fail on getting
Hi Tat,
First of all, thanks for putting the OS X release together - great work.
I have just been trying 2.0.0 pre 3, and have a few comments.
Overall, just about everything works, and it is very stable. I am
using OS X 10.4 on MacBook (Intel GMA 950 graphics chip set). I flew
from KSFO,
11 matches
Mail list logo
