Ah, indeed, I totally forgot those ! Sorry.dendwaler wrote:It does not work for me ,giving me the error message Python script fails, look into the console
Is it perhaps because i have several objects with an "non existing pagenumber" I have those for things that are not ready for export yet, for example : PyPRP can't export objects that are not textured.
Yeah. I preferred not using YAML for this reason. Actually I don't even have YAML anymore, since I had to download a 32 bits version of Blender, and I installed YAML on the 64 version.Deledrius wrote:If only Blender had a YAML module installed by default, we could avoid any manual entry at all:
(At first I was surprised to think it was a default module, but I realized I only had YAML in mine because I had tried your PyPRP update)
Good job ! If it weren't for you, we would probably all be clueless about how to use itDoobes wrote:Time to update and create some tutorials.
#import bpy
#
## put your pages with their number here
#pages = {
# 1: "your first page name here", # <-- you want to modify this
# 2: "your second page name here", # <-- you want to modify this
# }
#
## this copies game properties into page attribute for Plasma Objects
#for obj in bpy.context.scene.objects:
# for prop in obj.game.properties:
# if prop.name == "page_num":
# i = int(prop.value)
# try:
# obj.plasma_object.page = pages[i]
# obj.plasma_object.enabled = True
# except:
# obj.plasma_object.enabled = False
Nev'yn wrote:what are the conventions regarding software to release the Korman verison labeled 1.0?
Sirius wrote:My Age now exports without any problem, but I had to completely delete the biggest object - it caused Uru to crash at 3/4 of the loading bar (maybe it's because it used too many vertices ? Doesn't Korman check for objects that are too big ?).
So, I deleted that object, but now Uru crashes at the beginning of the loading bar. I had a quick look in the PRP, and I see it's missing the whole DrawableSpan ! DrawInterfaces are here, but they point to a nonexistant object, which Uru obviously hates.
Any idea what might be causing this ? My objects use only a single material with no texture or lightmap, and I am using two different pages (Uru loads the second page fine, but it only contains a single collider). Don't know if it helps I'll have a look later at removing some objects to see if there is an offending one...
Karkadann wrote:@ Adam
I never found an easy way to turn particle systems on and off in Max/Plasma,
would their be a way to do this in future versions of Korman?
Yeah, but manually deleting stuff in front of each line is as annoying as having to de-indent the textdendwaler wrote:You can post the code like this:
(after pasting the code uncomment it 1 time)
Oh, so the object is there, but PRPShop refuses to show it because it's invalid ? Interesting...Tsar Hoikas wrote:Interesting... Usually, when I saw objects being deleted from PRPs, they were actually in the PRP, just invalid. When PRPShop would read them back in, bad things would happen and they would be deleted. Korman should definitely be checking that the mesh is not too big... I wonder what's going on here. Does it still happen if you delete the other meshes aside from the problematic mesh? If so, I'd be curious to see the resulting PRP.
Sirius wrote:Oh, so the object is there, but PRPShop refuses to show it because it's invalid ? Interesting...
I'll test things further later, and report the result.
Yeah, but manually deleting stuff in front of each line is as annoying as having to de-indent the text
Sirius wrote:Anyway, I was wondering. How do you keep regions (which should be invisible) from being rendered by lightmaps or vcol ? Usually I just apply a material with zero alpha and raytracing disabled, but Korman hides the transparency panel in the material settings... Well, I can still use it if I switch back to Blender render, but it's not really convenient. And I'm afraid Korman will attempt to export the mesh as a visual if I apply a material to it...
Users browsing this forum: No registered users and 2 guests