> Yes I noticed that the new code was always 1c4 as well, but hadn't
> gone back to see what the old code was doing. But 1c4 definitely
> seems wrong since the vertex coordinates are all messed up and invalid
> according to MSDN. For example z is supposed to be [0,1] but I get
> large values, and
On 3/5/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> > On 3/4/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> I installed AOM (trial) here and I think the issue is related to the FVF.
> The function initializeFVF is only partially implemented and in case of the
> new code with my pa
> On 3/4/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> > Right now d3d8's SetVertexShader is disabled because d3d8 shaders don't
> work
> > using wined3d yet. Last week I experimented a bit with it and I managed
> to
> > get some simple vertex shader examples working (for instance
> > http
On 3/4/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> Right now d3d8's SetVertexShader is disabled because d3d8 shaders don't work
> using wined3d yet. Last week I experimented a bit with it and I managed to
> get some simple vertex shader examples working (for instance
> http://www.codesam
> It seems that during the porting of d3d8 to use wined3d some of there
> was some breakage. Age of Mythology was working fine, but now all
> vertex data is totally messed up (2D is menus and stuff is fine). It
> has been this way in CVS for the past few days, when I first noticed
> it. I though
It seems that during the porting of d3d8 to use wined3d some of there
was some breakage. Age of Mythology was working fine, but now all
vertex data is totally messed up (2D is menus and stuff is fine). It
has been this way in CVS for the past few days, when I first noticed
it. I thought it might
