Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Programmatic scene set-up #49

Closed
TOGoS opened this issue Feb 10, 2013 · 3 comments
Closed

Programmatic scene set-up #49

TOGoS opened this issue Feb 10, 2013 · 3 comments

Comments

@TOGoS
Copy link
Contributor

TOGoS commented Feb 10, 2013

I'd like to be able to select a world, select chunks to be rendered, and initialize render settings, and render an image either via command-line options or via some simple scripting language and without every opening the UI.

I started attempting to make this work but all the rendering methods are so closely tied to the UI that I didn't manage to get it to render an image and write it to disk. I figured I should at least ask you how feasible this would be before going and making a lot of changes that you might not want to merge back to the master branch.

(In case you're wondering, the use case for this, and also the reason I added the parallel projection, is to use Chunky to generate tiles for an overhead map.)

@llbit
Copy link
Collaborator

llbit commented Feb 11, 2013

I've been thinking about using a regular text file to store scene properties, this way all the setup could be done by a simple script, then sent to Chunky on the command-line. I think the most natural thing to do is use a regular .properties file, a standard that should work well.

@llbit
Copy link
Collaborator

llbit commented Feb 11, 2013

I added an issue for loading scene settings from a properties file here: #51

@llbit
Copy link
Collaborator

llbit commented Dec 31, 2013

Since version 1.2 the scene description format is JSON based. I think that this should make it sufficiently simple to set up scenes via scripting.

@llbit llbit closed this as completed Dec 31, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants