7th October 2008, 07:34 PM | #1 |
Junior Member
Junior member
Join Date: Oct 2008
Posts: 2
|
Exporting to Darkbasic Pro: texture problem
I made a simple cube in AC3D, textured it and then exported it as .x file to Darkbasic Pro.
Unfortunately, the cube isnt textured when loaded in Darkbasic ... what am I doing wrong ? |
8th October 2008, 09:07 PM | #2 |
Senior Member
Professional user
Join Date: Mar 2005
Location: Phoenix, AZ
Posts: 917
|
Re: Exporting to Darkbasic Pro: texture problem
The DarkBasic forums will probably be more knowledgable. I don't really know specifically for DarkBasic, but here's some general game-engine stuff:
1) Did you enable texturing in your engine? Most have a "render state" that needs changed to enable texture mapping. 2) Is your texture in a file format and size that the engine supports? 3) Is the path somewhere the engine can find the texture map? You might need to open the .x file in notepad to check. 4) Do your alpha channel \ materials need flipped? Some have transparent as zero, some as one, so sometimes you need to invert your alpha channels to make certain engines happy. 5) Did you checkmark include texture coordinates when you exported the .x file? |
9th October 2008, 05:08 PM | #3 |
Junior Member
Junior member
Join Date: Oct 2008
Posts: 2
|
Re: Exporting to Darkbasic Pro: texture problem
Thanks for your reply.
Now it works ... though I dont know why :? First time I tried it , I was using code for a FPS game which also includes collision detection ... texture wasnt visible. Now I made a simple program to only load an object and looking around with mouse and this time the texture is visible ! Not sure why it works with program B and not with program A... |
9th October 2008, 05:42 PM | #4 |
Senior Member
Professional user
Join Date: Mar 2005
Location: Phoenix, AZ
Posts: 917
|
Re: Exporting to Darkbasic Pro: texture problem
I'd bet something in the FPS project is changing the render state. Again, I'm not really the person to ask about DarkBasic, but in most game engines after you set a state it persists forever until something else changes it. So, there's probably some code in the FPS project that turns textures off to render some object that needs it, but forgets to turn it back on again before it goes to draw the next object.
|
|
|