NewsForumsCodeLogsGallerySpecsSearch

V105 gives a pointer?

Archives Forums/Blitz3D SDK Programming/V105 gives a pointer?

Leon Drake(Posted 2010) [#1]
So i went ahead and externed bbsystemproperty from V105, and it appears to actually be spitting out a pointer now. I'm not sure if it is the correct pointer or not.

I tried running an Initex function from fastextension and it doesn't crash until i try to use one of the bbcommands in the sdk. I'm guessing it does grab the device but could it be because all the function names in the sdk lib begin with bb that is crashing it?

The only other possible cause i could think of is it requires me to pass a type to the init function, i'm not sure if the byte ptr of the type i send through is going to work the same as a blitz3d type.

this is more or less what i have so far. 

Import blitz3d.blitz3dsdk
Import fastext.fastext
bbBeginBlitz3D()
bbGraphics3D 800,600,0,2

Print "Device "+Int(bbSystemProperty("Direct3DDevice7"))
InitExt									' <<<< 	Обязательно инициализуем после Graphics3D
											' <<<<    Initialize library after Graphics3D Function



cam=bbCreateCamera()'<----- crashes b3dsdk


this is the initialization function here

Function InitExt ()
	If FE_InitExtFlag=0 Then
		FE_InitExtFlag = 1
		FE_PivotSys = bbCreatePivot()
		DeInitPostprocess()
		InitExt_ ( Int(bbSystemProperty("Direct3DDevice7")), bbBackBuffer(), GfxDriverCapsEx )
	EndIf
End Function


the type for GfxDriverCapsEx is

Type GfxDriverCapsEx_Type

	Field BrushBlendsSrc
	Field BrushBlendsDest
	Field TextureCaps
	Field TextureBlends
	Field TextureMaxStages
	Field TextureMaxWidth
	Field TextureMaxHeight
	Field TextureMaxAspectRatio
	Field ClipplanesMax
	Field LightsMax
	Field Bump
	Field BumpLum
	Field AnisotropyMax
End Type

Global GfxDriverCapsEx:GfxDriverCapsEx_Type = New GfxDriverCapsEx_Type




perhaps this doesn't work in blitzmax?


Leon Drake(Posted 2010) [#2]
im just curious what pointer bbsystemproperty is returning. i tried it with different fields so i know the command is working. But for some reason the pointer its giving me to the directx device is either not correct or something isn't working with the initialization part in the module.