FVF Version - GameCreators Forum

Author

Message

Chiwawa

23

Years of Service

User Offline

Joined: 13th Oct 2002

Location: Canada

Posted: 11th Jul 2003 04:33

Link

hmmmmm in the help then write "version 336 is the default" ...

but in fact when you create a memblock from a mesh from..a primitive created in dbpro ... its the version 270..... and each vertice is 32..and not 36 byte then im asking wich component is not there..in this version? im taking a guest and i say: the diffuse color

but im not sure ill do some test...
hmm in fact it was a question but.. not its almost an affirmation.. anyway.. see by yourself:

DBPro V4.1

+ Code Snippet

sync on
sync rate 0

make object sphere 1,100

make mesh from object 1,1
make memblock from mesh 1,1

Version=Memblock DWORD(1,0)
Size=Memblock DWORD(1,4)
NbVertice=Memblock DWORD(1,8)

do
   set cursor 0,0
   Print "Version=",Version
   Print "------------"
   Print "(everything is in byte)"
   print "Size of Vertice=",Size
   Print "Vertice Count=",NbVertice
   Print "Size of memblock (without header)=",Size*NbVertice
   sync
loop

Back to top

Profile PM Email Website

haggisman

23

Years of Service

User Offline

Joined: 26th Aug 2002

Location: United Kingdom

Posted: 11th Jul 2003 11:19

Link

Yup they changed it from 336 to 274 by removing the diffuse color component of the objects. I guess they should have changed the help files as well.

project: light/obscurance mapper (85% done)

Back to top

Profile PM Email Website

Shadow Robert

23

Years of Service

User Offline

Joined: 22nd Sep 2002

Location: Hertfordshire, England

Posted: 11th Jul 2003 11:29

Link

ya both mad because it was 338 (you can't actually get 336 physically impossible)

Back to top

Profile PM Email Website

haggisman

23

Years of Service

User Offline

Joined: 26th Aug 2002

Location: United Kingdom

Posted: 11th Jul 2003 12:41

Link

Oops, i knew i shouldn't have copied that number off the first post

project: light/obscurance mapper (85% done)

Back to top

Profile PM Email Website

Rob K

Retired Moderator

23

Years of Service

User Offline

Joined: 10th Sep 2002

Location: Surrey, United Kingdom

Posted: 11th Jul 2003 13:41

Link

Not completely sure why they changed it to 274, but there must be a sound reason. Hopefully they will change it back to the much more useful 338, but it is pretty easy to change it.

Do you want Windows menus in your DBP apps? - Get my plugin: http://snow.prohosting.com/~clone99/downloads/tpc_menus_103.zip

Back to top

Profile PM Email Website

Chiwawa

23

Years of Service

User Offline

Joined: 13th Oct 2002

Location: Canada

Posted: 11th Jul 2003 15:26

Link

thx

sorry for the "336" i was rememering..the 33 and ..something round..like 6

Back to top

Profile PM Email Website

Shadow Robert

23

Years of Service

User Offline

Joined: 22nd Sep 2002

Location: Hertfordshire, England

Posted: 11th Jul 2003 16:07

Link

lol... if you want to know why they changed it from
(FVF_XYZ||FVF_NORMAL||FVF_DIFFUSE||FVF_TEX1)
to
(FVF_XYZ||FVF_NORMAL||FVF_TEX1)

then just look at my "Can anyone see whats wrong with this picture?" thread

Back to top

Profile PM Email Website

Rob K

Retired Moderator

23

Years of Service

User Offline

Joined: 10th Sep 2002

Location: Surrey, United Kingdom

Posted: 11th Jul 2003 16:52

Link

HEY!

CONVERT OBJECT FVF doesn't seem to work!

+ Code Snippet

make object cube 1,5

make mesh from object 1,1
make memblock from mesh 1,1

convert object fvf 1,338

make mesh from object 2,1
make memblock from mesh 2,2

do
   text 20,20,str$(memblock dword(1,0))
   text 20,40,str$(memblock dword(2,0))
loop

It's only today since I've returned to DBP coding for a break from Delphi that I've rediscovered how buggy it is - oh well - time to email Lee again. Hopefully it'll improve dramatically over the next month or two.

Do you want Windows menus in your DBP apps? - Get my plugin: http://snow.prohosting.com/~clone99/downloads/tpc_menus_103.zip

Back to top

Profile PM Email Website

IanM

Retired Moderator

23

Years of Service

User Offline

Joined: 11th Sep 2002

Location: In my moon base

Posted: 11th Jul 2003 16:53

Link

I've had no problem using the diffuse part of the vertex on any version from 3.1 upwards - in fact I was prototyping a landscape engine with it before I added textures.

I'll check out your other piece of code later when I get home.

Back to top

Profile PM Email Website

Shadow Robert

23

Years of Service

User Offline

Joined: 22nd Sep 2002

Location: Hertfordshire, England

Posted: 11th Jul 2003 17:31

Link

yeah Rob there's that for some peeps... but even if you created directly in the memblock specifying all the value - the bugger still don't work

Back to top

Profile PM Email Website

Chiwawa

23

Years of Service

User Offline

Joined: 13th Oct 2002

Location: Canada

Posted: 12th Jul 2003 01:30

Link

damn.... i dont know if its me...... or...

ok.. the old format was better ...... i mean this one:

Memblock-Mesh (32 Byte Header)
-Header
--4 BYTES (DWORD) Number Of Vertices
--4 BYTES (DWORD) Offset in Bytes to Vertice Data
--4 BYTES (DWORD) Number Of Normals
--4 BYTES (DWORD) Offset in Bytes to Normals Data
--4 BYTES (DWORD) Number of Faces
--4 BYTES (DWORD) Offset in Bytes to Face Data
--4 BYTES (DWORD) Size Of All Face Data
--4 BYTES (DWORD) Offset in Bytes to Texture UV Data
-Data
--Vertice Data
---For Each Vertex
----4 BYTES (FLOAT) - X Position of 3D Geometry
----4 BYTES (FLOAT) - Y Position of 3D Geometry
----4 BYTES (FLOAT) - Z Position of 3D Geometry
--Normals Data
---For Each Normal
----4 BYTES (FLOAT) - X Normalised Normal of 3D Geometry
----4 BYTES (FLOAT) - Y Normalised Normal of 3D Geometry
----4 BYTES (FLOAT) - Z Normalised Normal of 3D Geometry
--Face Data
---For Each Face (a face makes a polygon using A,B and C as vector points)
----2 BYTES (DWORD) - Number of Vectors in Face (always use 3)
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector A
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector A
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector B
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector B
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector C
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector C
--Texture Data
---For Each Vertex
----4 BYTES (FLOAT) - U Value of Texture
----4 BYTES (FLOAT) - V Value of Texture

+ Code Snippet

Memblock-Mesh (32 Byte Header)
-Header
--4 BYTES (DWORD) Number Of Vertices
--4 BYTES (DWORD) Offset in Bytes to Vertice Data
--4 BYTES (DWORD) Number Of Normals
--4 BYTES (DWORD) Offset in Bytes to Normals Data
--4 BYTES (DWORD) Number of Faces
--4 BYTES (DWORD) Offset in Bytes to Face Data
--4 BYTES (DWORD) Size Of All Face Data
--4 BYTES (DWORD) Offset in Bytes to Texture UV Data
-Data
--Vertice Data
---For Each Vertex
----4 BYTES (FLOAT) - X Position of 3D Geometry
----4 BYTES (FLOAT) - Y Position of 3D Geometry
----4 BYTES (FLOAT) - Z Position of 3D Geometry
--Normals Data
---For Each Normal
----4 BYTES (FLOAT) - X Normalised Normal of 3D Geometry
----4 BYTES (FLOAT) - Y Normalised Normal of 3D Geometry
----4 BYTES (FLOAT) - Z Normalised Normal of 3D Geometry
--Face Data
---For Each Face (a face makes a polygon using A,B and C as vector points)
----2 BYTES (DWORD) - Number of Vectors in Face (always use 3)
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector A
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector A
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector B
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector B
----2 BYTES (DWORD) - Index to Vertex in Vertex Data for Vector C
----2 BYTES (DWORD) - Index to Normal in Vertex Data for Vector C
--Texture Data
---For Each Vertex
----4 BYTES (FLOAT) - U Value of Texture
----4 BYTES (FLOAT) - V Value of Texture

i know.... its a littlebit bigger... BUT now each polygon is disconnected..... i mean in the old format you was able to take the same vertex..for 3 or 4 polygon..then when you were moving this vertex...all the polygon who touch to this vertex..was moving together... but NOW you have to move all the vertice who are at the same place....if not you will have some face not rendered..and hole in your object...... cause every 3 vertice are a polygon

Back to top

Profile PM Email Website

Shadow Robert

23

Years of Service

User Offline

Joined: 22nd Sep 2002

Location: Hertfordshire, England

Posted: 12th Jul 2003 07:40

Link

they're just using FVF format which is the inherint D3D Format, they could've wrappered it but really i don't think it matter much - i just wish they'd work out the kinks in the engine before rewriting it.

Back to top

Profile PM Email Website

Sorry your browser is not supported!

DarkBASIC Professional Discussion / FVF Version