[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Thread Index]
[Monthly Archives] [List Home]

Re: [Virtools] crashes with the new beta player??



Hi,
 
I'm using :2.0.0.33 on the computer i'm at now..
and it had problems of the same type mentioned, which were fixed by going a detonator version back...
Which I don't wanna do everytime there's  something wrong with the web player..
 
I can't say which version 's on our other pc's (i';m not at the office at the moment) but our fast machine.
( 1. 7 ghz geforce 3 etc. etc.) is practicaly unable to play the vmo's in IE at all.. due to crashes..which like I stated before, started with the last automatic update..
 
With regard to the texture format, we've had no texture problems  at all in dev 2.0, except some alpha blend modes appear differently in fog between d3d and opengl.
 
regards ,
 
tomas sala
 
----- Original Message -----
From: Regis Carlier
To: Virtools-User-Group (E-mail)
Sent: Wednesday, November 21, 2001 4:36 PM
Subject: Re: [Virtools] crashes with the new beta player??

Hello everyone,
 
We are experiencing the same problems using the web player,
like no textures using DX7, ie crashs, d3D not recognised.
going fullscreen with DX5 always crash the player.
 
Some of these problems could be fixed using the 16 bits 565 texture format.
this format seems to be the more efficient on differents 3D cards
 
Best Regards
 
-----------------------------------------------------------------
Régis Carlier
VP / Development Director
 
Studios SAVOIRfair
www.savoirfair.com


 
----- Original Message -----
From: tomas sala
To: Virtools-User-Group (E-mail)
Sent: Wednesday, November 21, 2001 3:54 PM
Subject: [Virtools] crashes with the new beta player??

Hi everyone
 
I'm experiences many crashes with the new webplayer beta,
as well as IE crashes, on some computers hardware d3d seems to unavailable..
also going to fullscreen results in crashes..
 
Am I alone experiencing this.??.
There's also a drastic performance difference between playing in dev 2.0 and in the weplayer..
It seemed to have happened when I received an automatic update about a week ago.
 
It could also be an conflict with the new direct X 8.1 which updated about the same time
 
regards
 
tomas sala
 
 

Follow-Ups: References: