Physics - Airplane

[Psychophanta]

Damn!
Here it is reached address 0 at line 300.
It hangs with PB6.10LTS win64 at windows 8.1 64bit

[Fred]

Ok, we understand you have an issue with the 3d engine, no need to post it on every topics, thanks.

[Psychophanta]

However, in previous versions it went fine

[pf shadoko]

@Psychophanta

as I've already told you, it seems to me that it is clear, InitEngine3D loads an old DLL
search for "engine3D.dll" on your computer, and see if you have an old version
maybe in the folder where unsaved code is executed (look in the preferences)

you can also try saving the code before executing it.

[Psychophanta]

@pf shadoko,
ok, and so, is it too hard for you to write:

Code: Select all

InitEngine3D(#PB_Engine3D_NoLog,#PB_Compiler_Home+"Compilers\Engine3d.dll")

instead of

Code: Select all

InitEngine3D()

With the first command all goes fine

Good demo, by the way

[Michael Vogel]

Extremly cooool!

I had a look where some simple modding could be done and the best procedure for doing so seems to be here:

Code: Select all

Procedure matiere(num,dx,dy,c1,c2, brillance=$888888,alpha=0,scale.f=1,flockcolor=0,flocktilt=0)

	Protected i
	
	CreateTexture(num,dx,dy)
	StartDrawing(TextureOutput(num))
	If alpha:DrawingMode(#PB_2DDrawing_AllChannels):EndIf
	Box(0,0,dx,dy,c2)
	Box(2,2,dx-4,dy-4,c1)
	
	If flockcolor
		For i=0 To 222
			Circle(Random(dx),Random(dy),Random(7)+2,Random(flocktilt)*$10101+flockcolor)
		Next i
	EndIf
	StopDrawing()

	CreateMaterial(num, TextureID(num))
	MaterialFilteringMode(num,#PB_Material_Anisotropic,4)
	ScaleMaterial(num,scale,scale)
	If brillance:SetMaterialColor(num, #PB_Material_SpecularColor, brillance):MaterialShininess(num, 40):EndIf
	If alpha:MaterialBlendingMode(num,#PB_Material_AlphaBlend):EndIf
	
EndProcedure

Here's the line to change the runway a little bit...

Code: Select all

matiere(1,256,256,$aaaaaa,$ffffff,0,0,1,$888888,30); was matiere(1,256,256,$aaaaaa,$ffffff,0)

[Fred]

@pf shadoko,
ok, and so, is it too hard for you to write:

Code: Select all

InitEngine3D(#PB_Engine3D_NoLog,#PB_Compiler_Home+"Compilers\Engine3d.dll")

instead of

Code: Select all

InitEngine3D()

With the first command all goes fine

Good demo, by the way

If you create an exe it won't work if you specify the compiler path. It's indeed an issue with another Engine3d.dll lying somewhere in your path so it gets loaded first.

[Psychophanta]

Indeed Fred, so the parameter for InitEngine3D() is hightly useful for those who have several PB versions installed.
Usually i do not create exe, that's why i just said i copied, pasted, and run, and it did not work, When i create an .exe i must joint to it the correct .dll. I know.

[pf shadoko]

@Michel Vogel
it's just a technical demo, I didn't try to make something pretty!

@Psychophanta
don't you think it'd be easier to fix your problem than to adapt all the 3D code just for you?
did you search for "engine3D.dll" files on your computer ?

[Psychophanta]

don't you think it'd be easier to fix your problem than to adapt all the 3D code just for you?

Again; maybe, but the good idea is to just copy, paste and run the demos, and avoid, if possible to have to adapt any code
Besides, what about users who use several PB versions?

[pf shadoko]

It works with several PB versions

did you search for "engine3D.dll" files on your computer ?

[Caronte3D]

No problems here.
Nice demo!

[Fred]

Having multiple PB version isn't an issue as long you don't put a PureBasic\compilers in your global PATH env var (you should never do that).

[skywalk]

Really cool demo.