Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Discussion / load object problem

Author
Message
sfmanga
19
Years of Service
User Offline
Joined: 18th Aug 2005
Location:
Posted: 19th Aug 2005 01:27
i am new to dark basic and programing . i am using blender for my objects but when i export them in .x format i can't load them in dark basic : load object"1.x",1 but it isn't working . there is no error but when i execute the program i see only a blue screen . whats the problem ????????
Grog Grueslayer
Valued Member
19
Years of Service
User Offline
Joined: 30th May 2005
Playing: Green Hell
Posted: 19th Aug 2005 04:48
Post your code in snips and upload the .x file.

NanoBrain
20
Years of Service
User Offline
Joined: 20th Jan 2005
Location: Portland, OR
Posted: 19th Aug 2005 07:02 Edited at: 19th Aug 2005 07:16
sfmanga,

I also use Blender, and have run into this same problem most of the time, when trying to display a .x model in DBC. This has hendered me, up until now, from "going through" with so many projects in the past.

However, on my last experimentations to figure out the cause of the problem, I came to a few questionable results. The model I experimented with last, was a combination of a few objects, converted to .x format as one whole object. Only some of the objects appeared on screen(see image below). But, with experimentation, by messing with the individual names of the objects from within Blender, I found that more of the objects visually loaded into DBC. However, not all of them.


Click on image for full view
Note:The image above only shows the head and torso object, when a full body should appear, instead. Also, the hip is rotated at a 90o angle, as compared to its rotation in Blender. This has to do with repositioning and rotating the objects from within Blender. However, I am not sure if it is due from the actions being done in Object or Edit mode.

Therefore, I pinpointed that the problem lay either in the length of the names of the objects, or the specific characters within the names. But, I am not sure. These experimentations gave me a path to follow, but with not full results or solid explaination as to why.

Maybe, you and I can figure this out together, by experimentation, and passing information of any results back and forth. Blender is a great tool, and I truly wish to configure its problem.


+NanoBrain+
sfmanga
19
Years of Service
User Offline
Joined: 18th Aug 2005
Location:
Posted: 19th Aug 2005 21:51
thanks . i'll try to experiment a little with object names and stuff. yes i agree that blender is an excelent modelling program . i'll make a post if i found out something
sfmanga
19
Years of Service
User Offline
Joined: 18th Aug 2005
Location:
Posted: 19th Aug 2005 22:11
i tried a little exporting objects and i found out that if you make for example a cube and subdivide it ,extruding and moving ,it will work in dark basic, but if you use subdivide->convert to mesh it will not work . and when you use multiple objects and just join them it also will not work . i think that maybe all the vertices of the object must be connected
TDK
Retired Moderator
22
Years of Service
User Offline
Joined: 19th Nov 2002
Location: UK
Posted: 20th Aug 2005 01:33 Edited at: 20th Aug 2005 01:37
[Edit] The last two posts appeared while I was writing this, so my comments are a little irrelevant now!

A few things to bear in mind:

1. The camera may not be pointing at the object. When objects are created they are automatically placed at 0,0,0 in space - unless you position them.

AutoCam off stops the camera automatically pointing at newly created objects, so if you have used it, don't forget to use Point Camera to aim at the object.

2. You may have the camera too far away from the object to see it.

3. The object you created may be too small to see. If you know you are definitely pointing the camera at the object, use Scale Object to increase it's size.

4. The object you created may be too big and if you are too close to it's X,Y,Z position the camera would be 'inside' the object which would render the object invisible. In which case, move the camera, use Scale Object to make it smaller or use Set Object to turn on the Cull flag so you can see the object's texture from the inside.

These may be totally unrelated to your problem and NanoBrain may be on to the real reason for your problem, but I thought I'd mention them anyway.

TDK_Man

Login to post a reply

Server time is: 2025-05-22 13:24:06
Your offset time is: 2025-05-22 13:24:06