pixelplucker Posted August 29, 2012 Share Posted August 29, 2012 I was testing ao using a prop next to an AM model to see if the prop gets included in the ao render or if it is ignored and just rendered normally. When I deleted all the lights and kicked up the ambient light to 80 being the only light in the scene AM crashes. Not sure if it's a bug or just me. Would be nice to be able to render imported objects with a little ao. ao_prop_test.zip Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted August 29, 2012 Hash Fellow Share Posted August 29, 2012 AO on props is actually new in v17 but it worked here in my quick test: Remember to set the Global Ambiance stuff in the Chor settings. I have a slightly later beta than the release v17. It's POSSIBLE it has some fix not in your version, but AO wasn't mentioned as an issue so I doubt it. Does it always crash for you? Quote Link to comment Share on other sites More sharing options...
Admin Rodney Posted August 29, 2012 Admin Share Posted August 29, 2012 When I deleted all the lights and kicked up the ambient light to 80 being the only light in the scene AM crashes. Not sure if it's a bug or just me. Would be nice to be able to render imported objects with a little ao. This sounds like it could be related to local memory. Make sure you save your Project prior to rendering to lock in any changes you've made. I assume this saving process frees up memory and (probably?) points A:M to the saved information on the drive rather than information stored in memory. General Rule: Saving often reduces variables. Quote Link to comment Share on other sites More sharing options...
pixelplucker Posted August 29, 2012 Author Share Posted August 29, 2012 Odd must have been gunked up memory, seems to be working now. Thanks guys! Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted August 29, 2012 Hash Fellow Share Posted August 29, 2012 The most annoying bugs in A:M are the ones that happen the first time I try something and then never happen again. It makes me feel like Gladys Kravitz on Bewitched. "But Abner, I swear there was an elephant in the Stephens' living room just five minutes ago!" Quote Link to comment Share on other sites More sharing options...
NancyGormezano Posted August 29, 2012 Share Posted August 29, 2012 When I deleted all the lights and kicked up the ambient light to 80 being the only light in the scene AM crashes. Not sure if it's a bug or just me. It may just be a problem with deleting lights and have nothing to do with AI in combo with props. I put in a bug report (which is reported to be fixed in next version) where there are only 2 bulb lights in the chor along with the ground plane. Sometimes when the 2nd instance of the bulb light is deleted, A:M crashes. If it doesn't crash then the 1st bulb light no longer illuminates the ground (scene is dark) (always). Since I couldn't get it to consistently crash, I'm not sure if the fix will address the crash problem. When it did intermittently crash, I believe I had monkeyed with turning on/off other properties, and/or I may have been trying to play with ambiance intensity before deleting the bulb. Quote Link to comment Share on other sites More sharing options...
pixelplucker Posted August 29, 2012 Author Share Posted August 29, 2012 That is a good possibility. I did delete the lights and AM did crash a couple of times in a row. Turning off the lights or maybe trying a really low value of 1 on them might be an easy work around. Strangely I reopened the file and it did work with Robs settings under the chor. I'll fiddle fart with that some more when I get some time. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.