blender tools & cylinders

I'm using Jass 1.x (not sure...) and all seems to be well.

However, I've observed something I don't understand, and I'd love an answer

1. Add a cylinder sculpt mesh, doesn't matter if it's oblong or not.

2. Take the top and bottom edges of the cylinder, scale them to zero in some axis (X or Y), thus "closing up" the cylinder. Bake and import into second life.

3. Create a prim, set it to sculpt, set it to cylinder, and load in your sculpt map...

Can someone explain why the top of the sculpt is not closed up, but the bottom is?

Thanks

Just tried it as I've never had any problems of that sort - still no problem. Mine closed both ends without a hitch.

I'm running Blender 2.49a with Primstar 0.9 add-on. The JASS options I have don't include a cylinder so I did it with the Primstar sculpt cylinder mesh.

You may get more assistance on Domino's website: http://www.dominodesigns.info/project/primstar

Ok, I downloaded the latest primstar (.9.16) from domino's site, moved jass out of the way, and took a crack at using it. According to the readme, you can tell it's setup properly if the add sculpt mesh is present in the add menu. It is

Problem #1: I can only add a mesh of type sphere. Clicking the text button thingy that says "Sphere" does nothing. Here is the exception listed in my Mac's console which occurs when I click the Sphere button:

Exception in Tkinter callback
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-tk/Tkinter.py", line 1414, in __call__
return self.func(*args)
File "/Applications/blender.app/Contents/MacOS/.blender/scripts/primstar/add_mesh_sculpt_mesh.py", line 385, in set_map_type
self.sculpt_menu.post(x, y)
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-tk/Tkinter.py", line 2705, in post
self.tk.call(self._w, 'post', x, y)
TclError

Problem #2: I cannot dismiss the add-sculpt-mesh dialog. Esc doesn't work.

Problem #3: Baking the sculpt map produces gibberish, and I mean serious gibberish. Nothing at all like the maps generated by Jass. The map I get looks something like a mountain range, all spiky. If only image posts worked on this forum

Problem #4: When I bake the sculpt map, I get no dialog or anything to configure the bake... Which means, I can't attach a watermark image, or tell it what I'm baking, centering, scaling, etc.

Back to Jass for now...

That's a leftover comment from the 0.5.x series scripts in the readme.txt, just seeing the menu options doesn't guarantee that 0.9.x is correctly installed.

#1) Looks like a problem with your Python / Tkinter installation.

#2) Trying clicking into one of the text fields then pressing Esc. This still may not work due to #1)

#3) That's the default LOD map. The bake never happened, probably due to #1

#4) This confirms the bake never happened, there is a GUI. Is there any further errors on the console?

Thanks for the reply Domino.

The interesting thing in all of this is that the Jass 1.41 stuff works flawlessly.

I did upgrade to Snow Leopard a while ago, but the python 2.5 install is still present and operational (like I said, Jass works fine). Snow Leopard does include python 2.6, but that's not being used.

I'm wondering if it has something to do with your theme work maybe? I notice that when the add a sculpt mesh dialog pops up, it looks different than the rest of blender, and very different from the Jass UI...

I'll dig around on the web and see if I can find a solution. I did try re-installing a fresh blender (the latest, 2.49b), but it didn't help

In all cases, I've been doing a manual install by copying the primstar folder into the scripts folder, as per your instructions. I've been doing it this way because the Mac version of blender doesn't seem to support a user scripts folder. When I've done this, I'm also removing the Jass stuff from blender to prevent any conflicts.

And yes, there is a bpydata folder already there.

If anyone listening has some ideas, I'm all ears

I'm sure the Mac version will support a user scripts folder, and it's a requirement of the 0.9.x scripts to be installed there. You can set it up in the Preferences window under "File Paths."

Ok, so I tested out the mac user preferences and that does work, so I switched my install to use your recommended install procedure. It didn't help at all

I then futzed around with the primstar gui code, and made a single change which brought it to life: After you define your ModalRoot class, I overrode the definition with this:

ModalRoot = Tkinter.Tk

Which essentially undid your class completely. When I run blender with that change, the menus work and the dialogs pop up, etc. Blender gets unstable, however, and the dialog pops up as a top level window...

So something in your ModalRoot class doesn't work properly on the Mac. I did notice a bunch of "win32" checks in the code and that leads me to believe that maybe this code needs a bit more debugging on macs

And, I made a cylinder as I described at the start of this bugfest, and it works as I had hoped it would

Updated:

I tried another experiment, and commented out this line in your code:

#self.overrideredirect(True)

In your ModalRoot class. If that line is commented it out, the menus work, but again, the modal dialog shows up as a top level window which then causes blender to crash...

So at least the issue there... Maybe someone can figure this out?

I'm just working on the export code at the moment, I won't be doing any more GUI debugging until that's done. However, I don't have a Mac so I'm not able to test on that platform.

Tkinter is designed to be a top level application GUI, so what I've done with the ModalRoot class is a wrapper to get it to play nice when run from Blender. The changes and different problems you are seeing are just exposing things I've already worked around. The problem is that this area of code needs a good understanding of the events occuring when the GUI is in use.

For example one of the things I had to allow for was Windows sending a "leave" event rather than a mouse click when you click outside the GUI (it also sends a "leave" when the mouse is moved outside the GUI. It might be that there is an oddball event like this on the Mac too.

The only way to track things like this down is to add a lot of extra debug prints into the code to trace what's happening. Obviously, this level of coding isn't appropriate discussion on this forum, so if you want to help debug this, come over to my site and post there, or raise an issue in the issue tracker. I can attach special test versions to dump out the info I'll need to get to the bottom of it there.