How to get a Space Lion from Blender into jME

Hello,

I wanted to experience the full way of getting assets from Blender into jME, only using the jME Wiki and my own skills, to discover the right workflow.
(FYI: I’ve got a good academic background in computer science, but also talent in the artistic field - so I can bring both worlds together quite well).

Blender, jME and the SDK have evolved quite well over the last years, and I’m very happy about what there’s available to all of us today.

Let me say that the Wiki was partially a good starting point in some ways, and a terrible misguide in other ways (especially the Normal Maps section).

I modelled a creature in Blender, based on the old 8 bit game “Wizard Of Wor” (my personal WOW memories).
I called this character “Space Lion”, but it is essentially a 3d version of the GARWOR (for those who remember the game).
As of now, it is fully rigged, skinned, sculpted and textured. The animations are still missing, the rig and skinning might also change slightly.
I found solutions to all problems that I encountered so far, and I spotted pitfalls and traps that someone with art+science background can explain quite well.

As all my work for this jME-Project will be Open Source and Creative Commons licensed, I’m thinking about going even a step further:
I will make a tutorial that I will call “How to get a Space Lion from Blender into jME” - and publish this as .pdf and .odt files for free.

You can then expect more and more of these kinds of material, that will be really really helpfull (at least for noobs).
This thread will be the spot where I will post my work. Maybe I can even answer some questions that might come up.

But I’ve got one question too: How can I publish my .blend, .png, .java, .pdf files here in the best way possible?
I could link to files on my webspace, but maybe you know a good ‘drop bucket thingy’ that is reliable.

8 Likes

Nice idea :slight_smile:

Would it be possible to do the tutorials as wiki pages instead though? Then they can be linked easily from the forums/appropriate other places on the wiki/etc ?

You should have edit privs on the wiki, just navigate to a page that doesn’t exist and select edit page from the menu at the top.

2 Likes

Yeah, I’d prefer the wiki version too but at any instance its much appreciated you want to share your knowledge.

Okay, then I’ll write it as Wiki pages.
Hopefully it can be converted to other formats quite easily afterwards.

So my question stays similar:
How do I post files in the Wiki? The blend files can (even with unpacked images) reach several MB.
Also, my textures are all 4k by 4k - so they will consume a lot of memory in the uncompressed .png version.

I could also put the stuff directly on Blendswap under CC BY 3.0 license.
I will create an account there in a couple of minutes…

We could add .blend as a supported format to the wiki… @sbook, do you know if DokuWiki supports that?

Editing and images are no problem, you can edit the pages, just go to a new one that doesn’t exist and use the menu all the way on the top to edit it.

These super big files contain the actual artwork/assets in several stages of production.
Any public hoster with some people behind it, but with no download limits, would be a good hoster for these.
That also kicks blendswap from my list of choice, because they have a download limit for free accounts.

I think that text and screenshots will also be okay, but not be enough, for the users to experience my tutorial.
I count in the order of somewhat between 25 and 100 MB that the users would get during the tutorial.
Typically wikis are not designed for large BLOBs, so a ‘drop bucket thingy’ would be good for the BLOBs.

<cite>@Ogli said:</cite> These super big files contain the actual artwork/assets in several stages of production. Any public hoster with some people behind it, but with no download limits, would be a good hoster for these. That also kicks blendswap from my list of choice, because they have a download limit for free accounts.

I think that text and screenshots will also be okay, but not be enough, for the users to experience my tutorial.
I count in the order of somewhat between 25 and 100 MB that the users would get during the tutorial.
Typically wikis are not designed for large BLOBs, so a ‘drop bucket thingy’ would be good for the BLOBs.

May I suggest giving a try to MEGA (https://mega.co.nz/) or Google Drive?

1 Like

Stuff on Google drive is less likely to be confiscated by the FBI.

2 Likes
@Ogli said: These super big files contain the actual artwork/assets in several stages of production. Any public hoster with some people behind it, but with no download limits, would be a good hoster for these. That also kicks blendswap from my list of choice, because they have a download limit for free accounts.

I think that text and screenshots will also be okay, but not be enough, for the users to experience my tutorial.
I count in the order of somewhat between 25 and 100 MB that the users would get during the tutorial.
Typically wikis are not designed for large BLOBs, so a ‘drop bucket thingy’ would be good for the BLOBs.

Again, the images will be no problem, DokuWiki doesn’t use a database for that. This site is run off our dedicated server which has lots of harddisk space and bandwidth so the general amount of data also would be no issue. Only the uploading :slight_smile: If everything fails you just pass us the files directly and we put them in the webspace.

1 Like

Google drive - don’t know if they would delete it when someone hasn’t used his account for, say, a year or so. I would like a system with redundant fallback and community.
This Mega will be run by Kim Dotcom, isn’t it? So I don’t know what to think of such a platform and its reliability. They also had security issues recently.
I should stick with the solution that normen proposed and send you the files directly.

In a couple of minutes, I will write my first wiki page for this community.
As usual, I simply start by copying the content of an existing page, like the blender-asset-page.
I have already a very cool idea for the overall design of the tutorial.

See you later, folks

1 Like

Hey Ogli, did you write it :D?

You need to wait a little more - I’ll have to recover from a health problem first.
The tutorial will be in the wiki soon.

I already made an addition to the ‘assets with blender’ page in the Normal Map section:
https://wiki.jmonkeyengine.org/legacy/doku.php/jme3:external:blender?&#blender_modeling_lowpoly_highpoly

Finally wanted to make that wiki tutorial … could not find any “create button”. I can edit existing pages, but don’t find a way to create a new wiki page.

Can anybody create a wiki page for me?
The name would be “space_lion_on_making_game_assets”
Thanks.

In my experience with wikis like this, you just put the URL in that you want and then you will have the option to create the page. It’s the most non-intuitive way of creating a page that I could conceive of but I’ve gotten used to it with these wikis.

I don’t know if that still works for ours but it used to.

Yes, I tried this, and a message from the wiki system is displayed, tells me this:

https://wiki.jmonkeyengine.org/legacy/doku.php/space_lion_test
->
“You’ve followed a link to a topic that doesn’t exist yet. If permissions allow, you may create it by using the Create this page button.”

But I don’t see a “Create this page button”.
I don’t know why I should not be allowed to.
Can you create a wiki site for me please?

See again ^^ the link (after a bit of htmlcode reading, the create button is commented out for whatever reasons)

Okay, but … the wiki is still somewhat unusable, just like the forum search.
This is how the image upload window looks (look at upper left corner):

I cannot click any of the buttons on the left side, neither can I read that widget.

Why didn’t you just keep the old system? The new website is defect.
Yes, it’s wordpress, but you cannot use this software in the current state.

It is not finished and complete yet.
But you can see the wiki article already:

https://wiki.jmonkeyengine.org/legacy/doku.php/space_lion_on_game_assets

:expressionless: