Elysian Shadows

JesseH wrote:I am working on a 2d (local multiplayer, as in ~use the same keyboard~ style) game that has gameplay similar to Gauntlet II on the NES. All the graphics at the moment are shitty placeholders, but the engine itself is looking quite nice. It is written in Lua, using LÖVE. I would give a repo link but it's private. :>
You can expect a release sometime mid-may. Do not hold me up to that though. :/

DistortedLance wrote:I've been working on a level editor of sorts (Qt/C++), and I think I'm far along enough to post something about it:



There are four tile layers (two for terrain and two for objects), as well as Collision and Entity layers (although entities are not implemented yet). You can see the current selection in the Sheet View dock widget, and the currently drawing selection in the main view to the right (it's in region-filling mode in the image).

Just a small list of features:

• Undo/Redo with shortcuts (working for all tile placement and collision placement)
• Copy/Paste tile selections (even across maps, although it'll look funny if the sheets are different)
• Tabbed map browsing
• Create new areas and open saved areas from the menu
• Rotate selection with arrow keys
• Zoom in and out of the map with Ctrl+Wheel (alternatively Ctrl+Minus / Ctrl+Plus; reset the view with Space)
• Multiple tile selection (there are four tree tiles selected in the image)
• Region-filling (fills the entire rectangular area with the selected tile(s); useful for filling the map with grass)
• Save and Save All prompts before quitting (I swear, it's an incredibly feature)
• Asterisks for unsaved maps (except for newly-created-though-not-yet-saved maps)

With the way I have it set up, you can't use any of the fancy placement modes with the Collision layer - the selection is always a single collision box, and it can't be changed (left-click to place and right-click to remove). Click-and-drag is available, but I don't know if it would be worth implementing other kinds of collision selections (I would either need a collision "palette" in the sheet view, or have the default selection to be a single collision box and allow for fancy collision selection). The most useful tool for collision, if I were to implement one, would be region-filling for large, straight sections of collision.

I'm using a ton of QGraphicsItems to represent the tiles (and they fetch the proper QPixmap and render their own decorations in their paint function), although I'm wondering if this has a significant effect on performance. So far, I find no performance issues except when switching maps (about a second to a second and a half when switching between large areas - say, 150x150 - and I think I know why this is). I'm wondering if using a QGLWidget would offer much of an improvement. I would love any advice from the more experienced Qt gurus on the board!

Also, there is no "Project" structure at the moment - everything is just "standalone", so to speak. I might change things around to have some kind of project-like cohesiveness to make it easier to link maps together (otherwise, there could be issues when renaming maps and such). I do, at the very least, have the darn thing properly fetching the relative paths of files when using the "Browse" button when creating new areas. Was such a pain when I forced my brother to test some stuff for me T_T

Stuff I could get done quickly if I didn't lack motivation would be area property editing (width, height, name, sheets) and a prettier Layer View (it's disguuuusting - and I don't even intend for Entity to be an editable layer (I plan for that to be done in a separate dock). I just stuck the radio button there because I was lazy).

The editor is completed to the point where I should probably work on an engine to actually utilize the maps it spits out. I currently have some rectangles testing the separating axis theorem -_-

TheBuzzSaw wrote:Falco, you're fired. DistortedLance will be taking over the next AiGD.

Click here to see the hidden message (It might contain spoilers)

DistortedLance wrote:I've been working on a level editor of sorts (Qt/C++), and I think I'm far along enough to post something about it:



There are four tile layers (two for terrain and two for objects), as well as Collision and Entity layers (although entities are not implemented yet). You can see the current selection in the Sheet View dock widget, and the currently drawing selection in the main view to the right (it's in region-filling mode in the image).

Just a small list of features:

• Undo/Redo with shortcuts (working for all tile placement and collision placement)
• Copy/Paste tile selections (even across maps, although it'll look funny if the sheets are different)
• Tabbed map browsing
• Create new areas and open saved areas from the menu
• Rotate selection with arrow keys
• Zoom in and out of the map with Ctrl+Wheel (alternatively Ctrl+Minus / Ctrl+Plus; reset the view with Space)
• Multiple tile selection (there are four tree tiles selected in the image)
• Region-filling (fills the entire rectangular area with the selected tile(s); useful for filling the map with grass)
• Save and Save All prompts before quitting (I swear, it's an incredibly feature)
• Asterisks for unsaved maps (except for newly-created-though-not-yet-saved maps)

With the way I have it set up, you can't use any of the fancy placement modes with the Collision layer - the selection is always a single collision box, and it can't be changed (left-click to place and right-click to remove). Click-and-drag is available, but I don't know if it would be worth implementing other kinds of collision selections (I would either need a collision "palette" in the sheet view, or have the default selection to be a single collision box and allow for fancy collision selection). The most useful tool for collision, if I were to implement one, would be region-filling for large, straight sections of collision.

I'm using a ton of QGraphicsItems to represent the tiles (and they fetch the proper QPixmap and render their own decorations in their paint function), although I'm wondering if this has a significant effect on performance. So far, I find no performance issues except when switching maps (about a second to a second and a half when switching between large areas - say, 150x150 - and I think I know why this is). I'm wondering if using a QGLWidget would offer much of an improvement. I would love any advice from the more experienced Qt gurus on the board!

Also, there is no "Project" structure at the moment - everything is just "standalone", so to speak. I might change things around to have some kind of project-like cohesiveness to make it easier to link maps together (otherwise, there could be issues when renaming maps and such). I do, at the very least, have the darn thing properly fetching the relative paths of files when using the "Browse" button when creating new areas. Was such a pain when I forced my brother to test some stuff for me T_T

Stuff I could get done quickly if I didn't lack motivation would be area property editing (width, height, name, sheets) and a prettier Layer View (it's disguuuusting - and I don't even intend for Entity to be an editable layer (I plan for that to be done in a separate dock). I just stuck the radio button there because I was lazy).

The editor is completed to the point where I should probably work on an engine to actually utilize the maps it spits out. I currently have some rectangles testing the separating axis theorem -_-

DistortedLance wrote: Actually, I've been trying to figure out a way to manage depth buffering.

SomeAwesomeUsername wrote:I've been working on this rts game with the gameplay style of Command & Conquer