Sign in to follow this  
  • entries
    45
  • comments
    48
  • views
    51690

Travels, and editing

Sign in to follow this  
hplus0603

230 views

I went to Paris over the week-end. Me and my sister took my mom as a present for her. We've been before, but a long time ago. Say what you want about the French, but they cook really well! I ate deliciously all week-end long. It's also always nice to hook up with family.

While returning to the airport, I would see occasional burned-out cars parked in the side of the road. Apparently, the French celebrate the fact that they've elected a new president by going out and torching random vehicles. I'm not sure I think that's really all that charming...

I haven't written in a while, but that's because I've made some progress! I have a just-in-time Lua debugger which shows up when compiling a Lua script fails. It allegedly lets you change the code right there, and try re-loading it. I've implemented it by suspending the main thread, and spawning a new thread that creates the debugger window and runs its own message loop. When the window is done, I release an event that the main thread is waiting on, and the main thread goes on. Unfortunately, there seems to be some interaction between the main window (which doesn't get messages while suspended) and the debugger window, so depending on when the breakpoint is hit, the debugger window doesn't respond to mouse messages. Annoying! I don't really dare put the message loop in the main thread, because Ogre probably doesn't take kindly to being re-entered.

I'm also getting closer to a usable UI for the editing functions. I'm soon at the point where I need some geometry to actually edit a level. You can see a screen shot here:



I'm running into all kinds of warts, though, that I don't understand, and that aren't in the specs. So much for my "no source is better" philosophy...


  • Ogre additive texture shadows don't clamp correctly at the edges (leading to streaking in the distance).

  • The mesh I use for locating the selection has really weird specular lighting, even though the material only calls out a little bit of it.

  • The weird window problem, which I believe to be message loop interaction, I talked about above.

  • oFusion CE, which I use to export geometry for Ogre, doesn't split-and-duplicate two-sided triangles, so proper lighting can't be done in that case.

  • oFusion CE also has a bug (fixed in the Pro version, which I can't really justify right now) where it doesn't display skinned characters. This makes creating animated characters, such as players, a challenge.



The first three I can probably debug if I break down and get the Ogre source download.
The fourth I can probably work around by writing it myself and doing a post-process on the meshes in question, although I am loath to do that, because it totally messes with the art path. It's bad enough that oFusion doesn't export version 1.4 meshes yet, and thus the mesh converter tool pass is really needed for best results.
Sign in to follow this  


1 Comment


Recommended Comments

Btw: the black stones, and the grass, are created as "cluster" object instances, whereas the trees and building are created as regular object instances. You can also see my component object model in action in the object properties window, where the "mesh" and "posori" components go together to make a "tree" object.

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now