New Alpha Consistant Error

Started by rcallicotte, April 28, 2008, 11:17:35 PM

Previous topic - Next topic

Oshyan

There is a memory leak that we're working on right now. Hopefully that will resolve these types of errors for simpler scenes.

- Oshyan

sonshine777

Quote from: Oshyan on April 30, 2008, 10:40:59 PM
There is a memory leak that we're working on right now. Hopefully that will resolve these types of errors for simpler scenes.

- Oshyan

So I guess we can sing the song "Theres a hole in your bucket dear Liza" ;D

Oshyan

Hehe, yes that would be very appropriate. ;)

- Oshyan

vissroid

not that its goin to help but...


I get it as well. lol

but personally its worth the use of more that one core to render which makes rendering much faster. lol

and those controls for the cam'. wonderful!

and being able to drag out and how you want on the croping of rendering specific areas. :D

so there. made it not all negative. :D

bigben

#19
I have had this too and can reproduce the sequence consistently, altough the occurence is intermittent (but frequent, 60-80%).

1: Start TG
2: Add an RGB imagemap (default projection is Through camera) - Error
    - (optional) Save file, restart TG or revert to saved, image loads OK and errors in following steps usually stop.
3: Change projection to Plany Y and set dimensions, image displays.
4: Change projection back to Through camera - Error
    - repeating 3 and 4 results in consistent behaviour.

If adding the image map succeeds, changing projections doesn't generate an error
5: Create new document and repeat adding an image map - problem may or may not occur
   - once the error occurs, points 3 and 4 above apply consistently
   - once the error occurs, Full render is black and takes a few seconds.
   - once the error occurs, saving the document and reverting to saved appears to fix the problem.

Memory usage with or without the error is around 100Mb RAM, 500Mb VM, 350 GDI
Test images were a 450x150 pixle JPEG and TIF.

Similar sequence looking at multi-threading.
1: Start TG
2: Set maximum threads to 1
3: Add an RGB imagemap (default projection is Through camera)
No errors, but display of image is intermittent.

And again:
1: Start TG
2: Add an RGB imagemap (default projection is Through camera) - If error occurs then proceed...
3: Set maximum threads to 1
4: Change projection to Plan Y and set dimensions, image displays.
5: Change projection back to Through camera - No error, image doesn't display


Hope this helps.

bigben

Another consistent error along a similar line

1: Create a surface shader
2: In the Fractal breakup section, create a new image map.
3: Reduce coverage - Error.

This is similar to the behaviour in the previous example in that saving the file and reverting to saved will fix things.

sjefen

All I need to do is play with Terragen for about 10 minutes or so, and..... baddaboom. There it is. xD
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

rcallicotte

I've had consistent memory errors no matter what.  I think I've had maybe three good renders from the Alpha.  Thankfully, I have the last version still available.  But, I think Matt said something about the next version shoring up some of these memory errors...whew.
So this is Disney World.  Can we live here?