next »

[pspeed]

So, those following along at home may know that I've been dallying in smaller side projects... each one part of a longer chain of things to keep me coding when I don't have much time to code.  Some "new shiny" to keep my head in the game, so to speak.

One of these projects has kind of come to fruition now and it's called SimArboreal.  It's a tree editor/generator that I showed pics of a prototype some time back.  Well, it's officially released and open sourced now.

A longer post is here:
http://hub.jmonkeyengine.org/forum/topic/simarboreal-formerly-tree-editor/

But here are some pics to whet your whistle.






Pretty much I just have to finish adding LOD support and then I can use it for the previous side track of the iso-terrain.  This was all part of trying to make a "quick" game that I could get some income from to offset medical bills.  "Quick" is relative when I can only spend a few hours a week on it, though.

[Michael]

Looks nice!

[Moonkey]

Oooh, fancy. You find time for the community when you can only spend a few hours of the day for computer stuff. You're such a kind person Paul

Edit: You can make some really good trees with this! With extreme detail too!

[pspeed]

Nice trees.

re: Community, yeah, there are a few reasons for this:

1) I need to "keep limber" and while I don't have large chunks of time uninterrupted, these little projects fit right in.  Unfortunately the next piece of Mythruna is one that's going to take me a large block of uninterrupted time so I'm putting it off until I know for sure I will have a whole week of full-time nights to deal with it.

2) I thought even if I'm not contribute to Mythruna, I can at least give my company a good name by contributing tools and resources.  If I can't finish my "big game" at least I can help others get to their goals.  Incidentally, I've recently reactivated and cleaned up the Simsilica twitter profile a bit: http://twitter.com/simsilica  (I'm not 100% happy with the angle on the logo but I like the idea of a silicon dioxide crystal)

3) These are all leading up to a small side-project that's actually a game.  One that I actually want to play myself.

[Michael]

My apologies, but I just woke up and started playing with it. In the end, the result is this:

EDIT: And it completely killed my framerate

[Moonkey]

My apologies, but I just woke up and started playing with it. In the end, the result is this:

EDIT: And it completely killed my framerate

That thing is amazing.

[pspeed]

Hahah... 2.1 million triangles for one tree.  Awesome.

[pspeed]

It concerns me a little that the colors are so messed up on your system.  I'm looking at the settings panel especially.  Not even close to right.

[Michael]

It concerns me a little that the colors are so messed up on your system.  I'm looking at the settings panel especially.  Not even close to right.

The panels didn't look like that, it only appeared as that when I took the screenshot.

[pspeed]

It concerns me a little that the colors are so messed up on your system.  I'm looking at the settings panel especially.  Not even close to right.

The panels didn't look like that, it only appeared as that when I took the screenshot.

Ah, it's probably because I'm using JME's standard screen shot app state and it saves the alpha of the scene in addition to the colors.  So anything that wrote last that had an alpha value ends up pulling in some of the default gray background.

[Moonkey]

It concerns me a little that the colors are so messed up on your system.  I'm looking at the settings panel especially.  Not even close to right.

The panels didn't look like that, it only appeared as that when I took the screenshot.

Ah, it's probably because I'm using JME's standard screen shot app state and it saves the alpha of the scene in addition to the colors.  So anything that wrote last that had an alpha value ends up pulling in some of the default gray background.

Is that why my screenshot appears to be much more vivid since I hit printscreen instead?

[Michael]

It concerns me a little that the colors are so messed up on your system.  I'm looking at the settings panel especially.  Not even close to right.

The panels didn't look like that, it only appeared as that when I took the screenshot.

Ah, it's probably because I'm using JME's standard screen shot app state and it saves the alpha of the scene in addition to the colors.  So anything that wrote last that had an alpha value ends up pulling in some of the default gray background.

Is that why my screenshot appears to be much more vivid since I hit printscreen instead?

Yes. I was contemplating on hitting printscreen, but I pressed every function key until it took a screenshot. I just didn't want to deal with the cropping.

[pspeed]

It's the print screen button that takes a screen shot.  So you must mean you hit "shift prt screen"... and yes that would be why yours was more vivid, I guess.

[Moonkey]

It's the print screen button that takes a screen shot.  So you must mean you hit "shift prt screen"... and yes that would be why yours was more vivid, I guess.

Shift prt screen? Keyboard layout must be different since I just have to press print screen.

[pspeed]

It's the print screen button that takes a screen shot.  So you must mean you hit "shift prt screen"... and yes that would be why yours was more vivid, I guess.

Shift prt screen? Keyboard layout must be different since I just have to press print screen.

On all of my keyboards, the print screen button is on the Sys Req button.  Regular press is Sys Req (which is the print screen button in the tree editor) and if I want to do a windows print screen I have to press shift.