(@Djes - Just saw, that it was a very old post getting bumped, so this is mostly to J. Baker).
Personally, I don't see the reason for embedding meshes. Your exe is gonna get massive real quick
and I guarantee you, that the majority is really not interested in your meshes, material scripts
or textures. There are LOTS of free stuff out there.
Anyway, if you feel it's REALLY important to "protect" your work...
Material scripts are simply text and can easily be imbedded.
Meshes can be embedded as binaries..I wouldn't do it myself, though.

Textures are images and can be embedded and fetched with catchimage()
ex:
Code: Select all
InitEngine3D()
InitSprite()
UseJPEGImageDecoder()
OpenWindow(0, 0, 0, 800, 600, "BlitzTest")
OpenWindowedScreen(WindowID(0), 0, 0, 800, 600)
Procedure.i CatchTexture(Index.i)
Protected tx.i, im.i
Select Index
Case 0
im = CatchImage(#PB_Any, ?TheImage)
Case 1
;
EndSelect
tx = CreateTexture(#PB_Any, ImageWidth(im), ImageHeight(im))
StartDrawing(TextureOutput(tx))
DrawImage(ImageID(im),0,0)
StopDrawing()
ProcedureReturn tx
EndProcedure
Debug CatchTexture(0)
End
DataSection
TheImage:
IncludeBinary "G:\atlantis.jpg"
EndDataSection
But..You never know...The team might implement your requests.
