|
VBBR
Moderator
Brazil
617 Posts |
 Posted - Jun 03 2004 : 3:58:07 PM
|
Hum, yeah I guess, because my GeForce2 MX (hem) supports 8 stages...
|
Whatever. Who knows... |
 |
|
|
masterbooda
Swordmaster
277 Posts |
Posted - Jun 03 2004 : 4:40:51 PM
|
I am not going to guess anymore, I am to happy that it is fixed... to me right now, I think it was just a combination of things, and that just seemed to fix it, there was no need for tex2 anyways, so no loss there....
DaBooda out... |
DaBooda Team is back: http://dabooda.789mb.com/ |
|
|
|
VBBR
Moderator
Brazil
617 Posts |
Posted - Jun 03 2004 : 5:35:16 PM
|
Wow, nine pages... this topic is going to mark VBGamer history 
Anyway, now you can continue developing the engine for good... |
Whatever. Who knows... |
|
|
|
sdw
Warrior
USA
160 Posts |
Posted - Jun 03 2004 : 8:34:40 PM
|
| Hey, Sr. Gaupo, my card is also a 9200 SE and I ran the test demo fine all along. Does the amount fo memory on the card matter? Mine's 128MB |
|
|
|
Sr. Guapo
Swordmaster
USA
272 Posts |
Posted - Jun 03 2004 : 8:45:37 PM
|
| It is possible, mine is only 64 MB, though I don't think it would... As far as I knew, a 9200 SE was identical to a 9200 SE, except for the speed/mem size... The supported features should be the same... |
|
|
|
masterbooda
Swordmaster
277 Posts |
Posted - Jun 03 2004 : 9:34:08 PM
|
I think it was something else all along, memory related yes, but not video related, it just reflected on the memory of the video card, I don't know if that makes any sense, but with directx there is a lot of stuff behind the scenes... so there is really no way of knowing...
DaBooda Out...
P.S. As for the cards being the same, they should have the same instruction set on both, the only difference being the memory...
|
DaBooda Team is back: http://dabooda.789mb.com/ |
|
|
|
Eric Coleman
Gladiator
USA
811 Posts |
Posted - Jun 04 2004 : 07:25:41 AM
|
The difference is the drivers. It's possible that some video driver's can compensate for a dispcrenpency in explicit stride and the FVF calculated stride. If you get either of those wrong, then you run into the possibility of the video card reading from memory that it possibly shouldn't be reading, and that can cause an error.
I suggest you read all the information the SDK has on what FVF means and how directX interprets its meaning. |
|
|
|
masterbooda
Swordmaster
277 Posts |
Posted - Jun 04 2004 : 09:20:07 AM
|
I would believe that the stride was the problem, but the fact that v1.0 ran with the same stride seems to contradict that idea.... I simply think it has to be something else, or I somehow made v1.0 skip that error, which is a possibility... all I know, now it is fixed and it was something that needed to be fixed...
DaBooda out... |
DaBooda Team is back: http://dabooda.789mb.com/ |
|
|
|
Sr. Guapo
Swordmaster
USA
272 Posts |
Posted - Jun 04 2004 : 11:47:33 AM
|
quote:
The difference is the drivers. It's possible that some video driver's can compensate for a dispcrenpency in explicit stride and the FVF calculated stride.
Is it possible that I could upgrade my driver (which isn't that old... January), and the original app would work? I was actually in the process of downloading a new one when masterbooda released the fixed version, so I stopped the download... |
|
|
|
EACam
Warrior
154 Posts |
Posted - Jun 04 2004 : 1:20:57 PM
|
I didn't read this WHOLE thread (goodness)...but it seems there is a misunderstanding of a very simple thing. I don't care about all the specifics and someone may have already answered this...BUT:
To get the size of the FVF just use a public constant and call it WHATEVER As Long (I'm not sure about the data type, check to see what the DrawPrimitiveUP wants for that param) and set it to a size at start up:
Dim tmpFVF As FVF
WHATEVER = Len(tmpFVF)
That works perfectly for me. Maybe I'm wrong, but can you get any simpler? Or perhaps your having a problem with something else. In that case, sorry for bugging up the already gargantuan thread  .
EDIT: And I have a crappy adapter too. |
Edited by - EACam on Jun 04 2004 1:23:46 PM |
|
|
|
EACam
Warrior
154 Posts |
Posted - Jun 04 2004 : 1:25:49 PM
|
9 pages? Such an odd number? Who wants to go for 10?
Sorry Eric, but this may spur pointless posts...like this one. |
|
|
|
masterbooda
Swordmaster
277 Posts |
Posted - Jun 04 2004 : 1:34:29 PM
|
Is this post the equivelent of beating a dead horse....lol
I would also like to know, if after you updated the driver, if it does work... just out of curiosity... as for the const fvf size thingy.... I did that, and the size on my end was a constant 32... maybe you can check what size it is on your end... maybe that will put this topic to rest...
I simply just did this Debug.Print len(texturestrip(0)), I did this at the begining of the engine, then one before the drawprimitiveup and after, and it was always a constant 32.....
Not to mention, and I cannot stress this enough, the fvf was set up the same in both engines, but on sr.Guapos it allowed the Tex2 in the fvf, and in Turbo it wouldn't allow it.... so To be honest, I answered the debug problem... but the reason is completely oblivious to me...
DaBooda out...
P.S. And if we keep going on this, we will soon explode the server and poor Eric will be picking up pieces of this debug for eternity... |
DaBooda Team is back: http://dabooda.789mb.com/ |
|
|
|
Sr. Guapo
Swordmaster
USA
272 Posts |
Posted - Jun 04 2004 : 1:58:15 PM
|
OK, this is going to annoy many people, but I installed the latest driver, and the original example ran fine. I even checked the FVF value in the source code, and it was set to tex2, so that was all I had to do all along... Wow, this is a little embarassing...
It still doesn't make sense why it ran in the original though... Oh well, the problem is solved, without too much major damage... |
|
|
|
Sr. Guapo
Swordmaster
USA
272 Posts |
Posted - Jun 04 2004 : 2:03:14 PM
|
| Oh, I also put in the debug.print statements, and I got the same thing: a constant 32 for the FVF size... |
|
|
|
masterbooda
Swordmaster
277 Posts |
Posted - Jun 04 2004 : 2:07:48 PM
|
ahhhhhhhhh....ahhhh......That is too funny.... but at least I noticed the Tex2.... it was an unnecessary use.... so there is always something to get out of this...
DaBooda out...
P.S. New drivers? unbelievable.....lol.... still doesn't explain v1.0.... but I will make a new demo and post it, see if there are any problems with the change....lol...here we go again... |
DaBooda Team is back: http://dabooda.789mb.com/ |
|
|
DrawPrimitiveUP error
