Shell 'Problem'

[katreeny]

.deb packages for 2.46 are available here: https://launchpad.net/~wgrant/+archive

Thanks for the pointer :-D From what I've seen so far, 2.46 is a big improvement on 2.45

Now to figure out that wretched texture exporting bit... Which is probably something super-duper-easy that I'm missing because I need to go pass out in preparation for another exciting day chasing bugs in corporate software...

Katreeny

[Jojon]

...just to confirm, the unzipped texture files need to be in the same directory as the .blend file?

Unzipped, yes -- not the files themselves, though, but the directory they are contained within. The search path in the .blend file is something like: project_directory/textures/$texture_name

[Robert The Rebuilder]

And if it is still not finding the textures, force blender to look into your textures directory:

- Bring up the UV/Image Editor panel
- From the Image menu, choose "Fix Broken Paths"
- When the file browser appears, click on the textures directory and click "SEARCH ROOT DIR"
- Save your blend file so that it remembers the new path

That should do the trick.

[Aloys]

I don't understand Valdez, do the objects in your Blender file show up as pink?

Robert: it appears this very useful option has been removed in Blender 2.46 I don't understand why..

[Robert The Rebuilder]

Robert: it appears this very useful option has been removed in Blender 2.46 I don't understand why..

Are you sure, Aloys? I have 2.46 installed, and the "Fix broken paths" option is still listed in the Image menu of the UV pane.

fix_broken_images_option.png (6.25 KiB) Viewed 5966 times

[katreeny]

I have the menu option. I also have the error:

Error loading script: couldn't open file /home/kate/.blender/scripts/blender/image_find_paths.py

And the script is not in the directory.

Katreeny (I will beat this wretched, finicky thing, I *will*)

Update: And some googling later I found the .py file and copied it into the appropriate directory, and now we have export happening. There may be something more than a shell with a cube after all

[Robert The Rebuilder]

Huh - why do you have a "blender" subdirectory of the .blender/scripts directory? I don't have one in my Blender 2.46 installation. What files are listed in that directory?

I recommend moving all files out of .blender/scripts/blender into .blender/scripts, then deleting the .blender/scripts/blender subdirectory.

[katreeny]

It's the way Ubuntu did it in the first place. Messy.

I may just delete blender altogether and reinstall everything to clean the whole deal up some. Except that for whatever the reason, the 2.46 install doesn't seem to include that file, so I'll probably need to do some reconstruction anyway.

On the plus side being able to drop the script where it's expected and then re-try it without having to exit and reopen the application is nice.

Katreeny

[Robert The Rebuilder]

I wonder if the 2.46 release doesn't include the image_find_paths script? When I uninstalled 2.45, I chose not to delete my scripts directory.

If this is the case, you and Aloys can download the script here:

image_find_paths.py

[katreeny]

Thanks, Robert!

I've now managed a successful export, and been able to test the shell. Now to see if I can manage something more than a shell with a big cube

Katreeny