Topic: The current state of the blender script file?

But why not commit to trunk directly and push too? Right now you are the only person working on the media branches and code reviews is hard to do in blender scripts.

While that is true, I don't think I'm confident enough in my knowledge in bzr to commit directly to the trunk. For now at least.

And thanks for the answers

Top

Quote

trimard wrote:

But why not commit to trunk directly and push too? Right now you are the only person working on the media branches and code reviews is hard to do in blender scripts.

While that is true, I don't think I'm confident enough in my knowledge in bzr to commit directly to the trunk. For now at least.

I do it this way (depending on the kind of change, you could make the changes directly in trunk, e.g. when just adding images):

1. Make a branch: brz branch trunk my_changes (assuming you are in the directory widelands-media-repo)
2. change the newly created branch, e.g.:
   - Add directorys: bzr mkdir directory
   - Adding files: bzr add path/to/file
3. cd to widelands-media-repo/trunk
4. run bzr merge ../my_changes
5. run bzr commit -m "description of change"
6. run bzr push (when pushing the first time it's bzr push :parent)

The last command pushes only the changes to launchpad, so not the whole 4GB are uploaded

Top

Quote

I do it this way (depending on the kind of change, you could make the changes directly in trunk, e.g. when just adding images):

Make a branch: brz branch trunk my_changes (assuming you are in the directory widelands-media-repo)
change the newly created branch, e.g.:
- Add directorys: bzr mkdir directory
- Adding files: bzr add path/to/file
cd to widelands-media-repo/trunk
run bzr merge ../my_changes
run bzr commit -m "description of change"
run bzr push (when pushing the first time it's bzr push :parent)

The last command pushes only the changes to launchpad, so not the whole 4GB are uploaded face-smile.png

Yes that's what I did, except for the merge part. Is that really necessary?

This is the result that I get when I render the Barbarian Lumberjack's Hut in Blender for Windows, version 2.76b:

aaaaa That's because it's not a problem with the scripts. It's the particle system that changed a bit in the new blender versions. I know I have the same problem with atlatean headquarter.

We ought to fix that case by case

Top

Quote

Forgotton: Maybe GunChleoc has to put you in the development team before you can push to trunk...

Top

Quote

Ok I'll try that after some tests. Seems a bit odd to me compared to git. I would like to make sure I understand what I do :P. Thanks for the help!

To stay on topic with the commits. What we really need is to render all the models > put them in a very simple format (like path_to_render = ../render/path_to_blend) and thus we would test in bulk all the blend that might currently bug (like the forester hut).

I think I will lose too much time trying to make the paths perfect. And I prefer to wait a bit that some older graphists can confirm the decisions. So on to that I go!

Top

Quote