Messages

Well that's unfortunate, I noticed it was down a day ago, now it seems we're restarting the year here

@KH - Plan on adding an interface once I get a little further.  I have one laying around that I been meaning to use.

@erico - Thanks for the feed back.  You'll notice that when it makes the vox it has a loading screen, that's what's missing at the obj writing phase which can cause major lag on large objects

I think I left a pink pixel in the original calculator strip, that came out good though, I haven't tried that one yet.

Some material values aren't being set yet either, so maybe those values are being set to some kind of default.

OBJ files are pretty big, but then they're actually written out as script, so converting it to another model format should reduce the file size greatly.

I've replaced the file with one that has a little loading display as the obj is being written, won't seem like its hanging.

Currently not, but I can add that in too.

Here's a demo video.

Taking that into consideration, I may just work on fixing normals and reducing the polygons.  You will still have the option between a full detail model and an optimize one.

Just be careful, as I don't have a loading phase for the obj creation like I do with the VOX, which means it crams all the processing together after doing the first model and could freeze on a highly detailed model...but if you're feeling daring, let me know where it craps out at.

As for the model, I'll just have to refine how it builds the structure, its sloppy, but functional.

Use a image strip(series of images in one vertical or horizontal tile) to create a VOX file(a raw 3d voxel model) which can be converted in Slab6 to be used with build engine or whatever else.

Also exports a DDD file, glbasic model file and a OBJ w/ MTL files for use in other projects.

This is just a beta, so the OBJ doesn't have proper normals defined, nor is it optimized much.

It also creates a MTL file with the object which includes all the color info.

As a simple test, I ran a 16x16x3 strip, opened the obj in Anim8tor, export it as a 3ds, and then used poly2vox to convert it into a voxel again.  Its not worth the effort though as poly2vox creates some garbage pixels even if the models is made of cubes.  Still, a fun test, and the color data was retained in the 3ds.

However, my next step before I start to optimize the model building is to allow you to reverse a VOX file into a model.

The normal issue seems to be simple, and I just kind of threw empty ones in for now, just will take some tweaking.

I renamed the DLL like the post talked about, but now I get this.

Code (glbasic) Select Expand


Problem signature:
  Problem Event Name: APPCRASH
  Application Name: EditorE.exe
  Application Version: 2011.61.0.0
  Application Timestamp: 4d6e4dcb
  Fault Module Name: MSVCR100.dll
  Fault Module Version: 10.0.30319.1
  Fault Module Timestamp: 4ba1dbbe
  Exception Code: 40000015
  Exception Offset: 0008d635
  OS Version: 6.1.7600.2.0.0.768.3
  Locale ID: 1033
  Additional Information 1: 2038
  Additional Information 2: 2038ea2b560801aefc70fdb5df6daffd
  Additional Information 3: 859a
  Additional Information 4: 859a77c639ddf82b730cdba94ef86d57


I haven't tested older versions, maybe I shouldn't of updated before seeing if it ran.  I have no idea what that DLL is for either.

I recently got a new system with Win 7, I just installed 9, updated it and the editor crashes upon opening.

Code (glbasic) Select Expand


Problem signature:
  Problem Event Name: APPCRASH
  Application Name: EditorE.exe
  Application Version: 2011.61.0.0
  Application Timestamp: 4d6e4dcb
  Fault Module Name: psdprotect.dll
  Fault Module Version: 3.1.212.0
  Fault Module Timestamp: 4bfd066b
  Exception Code: 40000015
  Exception Offset: 0000b1f3
  OS Version: 6.1.7600.2.0.0.768.3
  Locale ID: 1033
  Additional Information 1: 2f4c
  Additional Information 2: 2f4cfd7e1c974028cc61cc7f7de22d55
  Additional Information 3: 35a3
  Additional Information 4: 35a3a6258e80d3502d74f84c5470a697


You should limit the draw update to 30FPS, in other words skip every other frame.

I knew today would be a good day to check the forum.

I don't see why not, everyone will just ignore them anyway and you'll get some cash

I think the problem happens on systems with 32bit color instead of 24bit.

I'd use the sprite2data functions to convert the data to an array but this also doesn't work on all systems.  Although I haven't tried it with different color modes yet.

When switching to 16bit color, I found my getpixel command was much more accurate.

I haven't tried other things that have had issue on different systems yet.  Grabsprite tends to work on some computers and not others.

Lately I found my get pixel routine was very off, completely ignoring white against black in some areas.  But switching to 16bit allowed it to properly function.