Help -- Render Issues

myutogarumyutogaru Posts: 60

So I posted this in technical problems or whatever, but I really need someone to get back to me ASAP because this is getting  ridiculous. Every time I try to render ANYTHING with a distant light and Raytrace OR Deep Shadow i get this error... I've gotten this before, it fixed itself, but now I cant fucking render anything and it's pissing me off. I'm sorry for my obscene, vulgar language but I'm so frustrated. I spent hours on a project and then I cant even see the finished product. It's ridiculous...Anyone know what the problem could be? fixmypcmike attempted to help before, but I just realized it was the shadows that were causing the Error. 

 

Windows 7 Home Premium (service pack 1)

intel(R) celeron(R) cpu 900 @ 2.20ghz 2.19ghz

2gb RAM

I've rendered with raytrace and deep shadow before, and I just did a defrag and disk clean up and i freed up a bunch of space. But if it's a RAM issue then I dont know what to do. please help

DAZ Error Scrnsht.jpg
1366 x 768 - 234K
Post edited by Chohole on

Comments

  • myutogarumyutogaru Posts: 60
    edited August 2015

    EVERY TIME I ATTEMPT TO RENDER IT GIVES ME THIS

     

    What is the problem?! I havent been able to f***ing render for DAYS.

    Windows 7 Home Premium (service pack 1)

    Intel(R) Celeron(R) CPU 900 @ 2.20GHz 2.19GHz

    2.00GB RAM

     

    I've gotten this before but it fixed itself within 5mins of just waiting.

     

     

    DAZ Error Scrnsht.jpg
    1366 x 768 - 234K
    Post edited by myutogaru on
  • myutogarumyutogaru Posts: 60
    edited August 2015

    Accidentally put a .png heres the Error

    Post edited by myutogaru on
  • fixmypcmikefixmypcmike Posts: 19,583

    2GB of RAM doesn't allow much at all -- even if you close all your other programs, you won't be able to get much into a scene.  First, try just creating a primitive cube and seeing if that renders.  Textures tend to use up the most memory -- you could make copies of the textures you use, shrink them, and use those to cut down on memory use.

  • Okay, I'll try your idea and if it doesnt work I'll be back.

  • I just rendered a cube and it worked perfectly.. So maybe the textures are making it crazy.. _sigh_

  • Also for some reason I keep getting "Optimizing Images" which i very rarely used to get, once that started happening again I kept getting the errors. Please help

  • fixmypcmikefixmypcmike Posts: 19,583

    Try this:  once your scene is ready, save it and close DAZ Studio.  Give it a few minutes to do its cleanup (you can open Task Manager and on the Processes tab wait for the dazstudio.exe process to finish).  Start DAZ Studio and load your scene.  Once the scene has finished loading, wait a few minutes so it can do the Optimizing Images in the background, and then try rendering.

  • myutogarumyutogaru Posts: 60
    edited August 2015

    Thanks!! It's working better now :D

    I take that back, it's something wrong with the lights and shadows... I attempted a render with Raytrace and it gave me the error. I used Deep Shadow Map and am currently rendering as I type this. I'm not sure what the problem could be

    Post edited by myutogaru on
  • FishtalesFishtales Posts: 6,119

    If you only have 2GB of ram then you should get more as that is even too low to run Windows 7 properly.

    Either put the Motherboard information in here or let it scan your system and it will tell you your upgrade options.

    http://uk.crucial.com/gbr/en/index

    It is quite safe. I have used them a lot over the years yes

  • ChoholeChohole Posts: 33,604
    edited August 2015

    Threads merged. Please don't start duplicate threads on the same issue, especially as you have already received help in the first thread.

     

    If you wnated the thread moved to another foum, please ask a member of the Forum Team to move it, by clicking the flag under your post and explaining.   Thanyou

    Post edited by Chohole on
  • JD_MortalJD_Mortal Posts: 760
    edited August 2015

    I would blame it on RAM also...

    I would suggest this... Save the project/scene after you have set it up. (Including the camera setup to the actual point where you will render the view.)

    Close DAZ, wait a moment. Restart DAZ, and ONLY load that scene, jumping right to the camera view.

    While in the camera view, open the scene-view, and start "Hiding" things which are not going to be rendered. (DAZ is trying to digest all of that data, to determine what is and is-not seen, prior to rendering. Hiding unseen things should resolve most of that "Is this in view, does it need reduction", thinking.)

    With that done. Save the scene as a new scene, titled "Whatever_Optomized", so you can edit that one later, but not harm the original one with all the stuff visible, or if it crashes again, you don't have to do that hiding all over again.

    Also, check to see if you have some kind of super-HD values or environment settings that are crazy high, and not needed, Like rendering the ground, which you can't see, or the environment. (Always go lower, then up the details of the render as needed. 95% of the time, some simple post-editing of the image is faster than trying to render deep shadows and contrast, or colored-lighting effects, with simple editing of GAMMA, CONTRAST, HUE ADJUST... etc, in any paint program, or online-image editor. Unless you are rendering deep-fog or extreme focal-lengths that standard blurs and hand-painted alpha-fog can't recreate... then don't kill your PC trying to render those minor one-shot effects.)

    Also, check if you have HD-textures loaded and enough "system cache memory" (Virtual memory/Swap Memory) available, as well as enough disk-space where your temp-files are. (Use disk-clean-up and try defragging to consolidate all your file fragments which will stop programs like this which attempt to harvest whole-chunks of unfragmented virtual-memory directly, and sometimes can't.)

    Also... Turn off any virus scanners. They attempt to capture anything headed into RAM into a super-small virtual-swap, for "scanning", before releasing the actual files into windows-control, which goes into non-virutal RAM. (Eg, they run in a sort of virtual windows environment to trap and detect virus-like activity, such as attempting to alter system files. Keeping them our of real RAM, and out of permission of system-files, in the virtual-RAM, allows them to be intercepted. However, it does not have the full size of your system-swap, obviously.)

    Last... There is a stand-alone program for rendering, and DAZ is already setup to shift work to be rendered to it. You change the output to... um... I forget.. Have to look that up... But then you open that file it creates, which is just your whole project, with the stand-alone IRAY after closing DAZ, and it renders outside of DAZ, freeing-up a LOT of memory, as you are not rendering AND trying to display the whole project rendered in DAZ in the editor window.

    Ultimately... You need more RAM. Windows XP demanded 2GB, Vista demanded 4GB, Win7 demanded 4GB, and Win8 was 8GB... Win10... I bet is still 8GB. I personally use 16GB, but nothing has ever come close, with all the things I have open, filling that. (Yet, still some programs complain about being low on memory because THEY can only allocate 2GB or 4GB of RAM, per thread. EG, poor programming.) * Demanded = To get the 100% score for RAM, not as an actual minimum... They all can run off 1GB. (Mini-ITX is proof of that. THey just don't run well, or do much. :P)

    RAM is cheap. 16GB DDR3 is like $40.00 USD, 8GB DDR3 is like $15

    Post edited by JD_Mortal on
  • ChoholeChohole Posts: 33,604

    Of course another problem here is the age of the PC,  That is a single core machine,

  • myutogarumyutogaru Posts: 60
    edited August 2015

    Well, what's weird is, I can render V7 with Leyton hair without any lights or shadows. Once I add those things it fails. So maybe i should just do it all in Photoshop.... *sigh* I appreciate all your advice and will try it all. I'll probably just get more RAM and hope that helps. If it doesnt then.. I dont know.

    Post edited by fixmypcmike on
Sign In or Register to comment.