OTOY Forums

Ok thanks marcus

i'll try and leave you alone now and get on with trying to break 2.48C

I was running 2.47 whilst using Photoshop CS5. The two seemed to live together quite happily. The render had been building for 24 hours when I opened PS. The exact work flow was that I saved the render from Octane, opened PS in order to make changes and to convert to a jpeg. All this time the render was still running.

When the crash happened I was running Octane 2.48 whilst modelling in Blender 2.58.1. I probably had the Chrome browser running at the time with a reference image displayed from google.

When I get back from work I will fire up 2.48 again and see if I can break it by doing various things at the same time.

steveps3 wrote:I was running 2.47 whilst using Photoshop CS5. The two seemed to live together quite happily. The render had been building for 24 hours when I opened PS. The exact work flow was that I saved the render from Octane, opened PS in order to make changes and to convert to a jpeg. All this time the render was still running.

When the crash happened I was running Octane 2.48 whilst modelling in Blender 2.58.1. I probably had the Chrome browser running at the time with a reference image displayed from google.

When I get back from work I will fire up 2.48 again and see if I can break it by doing various things at the same time.

Thanks for that. Maybe try the new beta 2.48c and have an eye on the available memory in the viewport status bar.

Cheers,
Marcus

Yeah, will do. I did notice that it was showing an available ram of 1912MB the other day which was higher than the 2.47 version shows. 1912MB out of 2GB sounds good to me. Just wondering what is sucking up the rest seeing as how it is used for nothing other than rendering Octane. Anyone seen my 112MB?

I will check in 2.48c. I think that under 2.48b I was using around 1.5GB of ram, give or take.