okay... I REALLY want to use this program but it's being a pain.
When I boot up the program it works good and I can select chunks and stuff but when I press render the 3d viewer comes up and this little message box shows up in front of it and says "could not open render directory" and I went to system 32 in the windows folder and made a scenes folder but the same message comes up! I've tried everything and it's frustrating!!
help please?
-Nixrokn
p.s. I;m not really smart with technological terms so speak ENGLISH please.. lol
What operating system are you using and where did you place the Chunky.jar file?
Ohmygod. This is amazing. Thank you so much. Now I can make awesome minecraft backgrounds.
Rollback Post to RevisionRollBack
When life gives you a potato, wonder why the heck life just gave you a potato. Why not something else? Like money? Or a combustable lemon? No, you get a potato. Nothing else.
am I missing something? Rendering indoor scenes is a PITA.
Emitter intensity all the way up, I gave up on this one at this point:
canvas size: 1600x1200
rendered for 21 hours, 15 minutes, 16 seconds
213713 samples per second
16352640k total samples
8517 samples per pixel
and it looked like this:
(click for full size, and to see just how grainy it is)
I'm assuming that's due to the mall surface area of the light emitting elements of torches; each ray has a smaller chance of hitting it. Switching them out for glowstone blocks (or editing the code so torches act like glowstone )fills in the scene a bit quicker, but it's still a roll of the dice if a pixel sends out a ray that eventually hits a light source. It seems like something with a half life. At x minutes, half of them might be visible. At x*2 minutes, 3/4ths. x*3, 7/8ths. I could be waiting forever for every pixel to finally hit a lightsource.
Hi everyone. I want to notify those who read this thread that a new version is out!
Today version 1.0.10 has been released! In this version Chunky will ask the user where to save scene descriptions and rendered images. This will fix the problem some users had with Chunky attempting to write files to System32 (because the current directory for the Java runtime was not correctly set).
I don't check this thread as often as I check the subreddit at http://www.reddit.com/r/chunky, so if you are a reddit user and you have feedback or want to share rendered images I suggest that you post there!
I'm assuming that's due to the mall surface area of the light emitting elements of torches; each ray has a smaller chance of hitting it. Switching them out for glowstone blocks (or editing the code so torches act like glowstone )fills in the scene a bit quicker, but it's still a roll of the dice if a pixel sends out a ray that eventually hits a light source. It seems like something with a half life. At x minutes, half of them might be visible. At x*2 minutes, 3/4ths. x*3, 7/8ths. I could be waiting forever for every pixel to finally hit a lightsource.
Is this just not meant for indoor scenes?
Yes you are correct, it is due to the small surface area of the light sources.
What you are experiencing is the slow convergence of the Monte Carlo path tracing method. If you wait longer, the image will become less grainy. Unfortunately, the graininess reduces less and less for each additional sample. It's an exponentially slower process.
There is not much to do about this problem, it is intrinsic to the rendering method. I will add another rendering method (progressive photon mapping) in the future which will likely give different results. In the meantime this kind of low-light scenes take a very very long time to render.
In my own experience I have always been able to reduce the graininess and get an acceptably smooth image, but in some cases this required days of rendering.
You could try to render the image at a lower resolution, this increases the rendering speed.
There is something I am wondering about... I have a computer with 8gb... allocated 6gb for chunky... and the render for a 600x400 picture is by now running 10 hours and it is still telling me that it is not yet finished while using all available cpu's to maximum...is that normal with chunky?
It doesn't tell you when it's finished, you stop it when you think it looks good enough.
Rollback Post to RevisionRollBack
I'm a Java programmer, and I'm a terrible artist. Anything else, just ask me.
I can't open the .jar a second time. I'm guessing it's because I didn't close it the "right" way when I used it for the first time, and now javaw.exe is running or something. I tried deleting all java processes, but it still won't start.
Did you try restarting your computer maybe?
Rollback Post to RevisionRollBack
I'm a Java programmer, and I'm a terrible artist. Anything else, just ask me.
Please help! I only ran it one time, and when i tried again it wont open! PLEAS TELL ME WHAT TO DO!
Some users seem to have this problem. You can try to delete the .chunky folder (yes, the period is part of the name) in your home folder (My Documents or Documents on Windows).
I'm using windows 7 64 bit and my jar file is in the downloads section but does the new update fix my problem?
Yes, I believe that it should fix your problem. The program will now ask you to specify a directory where renders and scenes should be saved. If the default directory does not work, you can specify a custom directory there, as long as your Windows user has write access to the directory it should work fine.
Okay Thanks! my friend is having a problem where he used the program once and then now when he tries to open the chunky.jar file it won't open and the bat file doesn't work either he says...
any ideas?
Pretty nice! I don't like the UI but I suppose it's serviceable and better than some unix-like CLI
Ingame mods have issues with viewrange etc, Chunky renders it all no matter what. Including shadows which is really nice. Also I can decide when the image is "good enough" so I don't need to render for 45hrs if I don't want to.
was done in 5mins. I need to look at this program more closely later when I have something worth rendering.
What operating system are you using and where did you place the Chunky.jar file?
Chunky does not do any texture interpolation or filtering, so the textures will look pretty much as blocky as they do in regular vanilla Minecraft.
Also, where are some places I can get some skymaps at?
Emitter intensity all the way up, I gave up on this one at this point:
canvas size: 1600x1200
rendered for 21 hours, 15 minutes, 16 seconds
213713 samples per second
16352640k total samples
8517 samples per pixel
and it looked like this:
(click for full size, and to see just how grainy it is)
I'm assuming that's due to the mall surface area of the light emitting elements of torches; each ray has a smaller chance of hitting it. Switching them out for glowstone blocks (or editing the code so torches act like glowstone )fills in the scene a bit quicker, but it's still a roll of the dice if a pixel sends out a ray that eventually hits a light source. It seems like something with a half life. At x minutes, half of them might be visible. At x*2 minutes, 3/4ths. x*3, 7/8ths. I could be waiting forever for every pixel to finally hit a lightsource.
Is this just not meant for indoor scenes?
Today version 1.0.10 has been released! In this version Chunky will ask the user where to save scene descriptions and rendered images. This will fix the problem some users had with Chunky attempting to write files to System32 (because the current directory for the Java runtime was not correctly set).
I don't check this thread as often as I check the subreddit at http://www.reddit.com/r/chunky, so if you are a reddit user and you have feedback or want to share rendered images I suggest that you post there!
Yes you are correct, it is due to the small surface area of the light sources.
What you are experiencing is the slow convergence of the Monte Carlo path tracing method. If you wait longer, the image will become less grainy. Unfortunately, the graininess reduces less and less for each additional sample. It's an exponentially slower process.
There is not much to do about this problem, it is intrinsic to the rendering method. I will add another rendering method (progressive photon mapping) in the future which will likely give different results. In the meantime this kind of low-light scenes take a very very long time to render.
In my own experience I have always been able to reduce the graininess and get an acceptably smooth image, but in some cases this required days of rendering.
You could try to render the image at a lower resolution, this increases the rendering speed.
On the Wiki there is a link to this place: http://www.wuala.com...tikz_360_Skies/
This is cool! I just got it for my mac, and I ran it once (it worked successfully) then when I went to open it again, nothing happned. What do I do?
It doesn't tell you when it's finished, you stop it when you think it looks good enough.
I wish I could help but sadly I don't own a mac so I can't tell you exactly what the problem is.
What are your mac's specs? Maybe if it's running slow it might not open, I find that happens on slower computers.
What version of Java are you running?
Also, you could try completely deleting the file and downloading a new one.
nrub,
You should add some example photos to the OP.
Heres what I've got for ya:
Did you try restarting your computer maybe?
Download link: https://launchpad.net/chunky/trunk/1.0.11/ download/Chunky-1.0.11.zip
Some users seem to have this problem. You can try to delete the .chunky folder (yes, the period is part of the name) in your home folder (My Documents or Documents on Windows).
Yes, I believe that it should fix your problem. The program will now ask you to specify a directory where renders and scenes should be saved. If the default directory does not work, you can specify a custom directory there, as long as your Windows user has write access to the directory it should work fine.
Thanks!
Also, you may go ahead and post them on the wiki, as long as you put it was taken by me.
any ideas?
Your program is very nice.
I would like to share a quick render that I did.
I'm just saying let's remove all the warning labels and let the problem sort itself out.
Best. Build. EVER.