Jump to content
Hash, Inc. - Animation:Master

genocell

Craftsman/Mentor
  • Posts

    177
  • Joined

  • Last visited

Profile Information

  • Location

Previous Fields

  • Hardware Platform
    Windows
  • System Description
    I put two wires together to start-up my computer.

genocell's Achievements

Journeyman

Journeyman (4/10)

0

Reputation

  1. I've been out of the loop for a while. What are the new features to be expected in the new release? I'm up for a new subscription and I'm curious.
  2. Okay. I'll keep that in mind. Thanks.
  3. V13. The problem started when I upgraded to v15. I don't normally use save under projects until recently. It doesn't happen when I do a project/cho from scratch. But when I use any project with the same models it will sometimes render weird. If the problem render starts in a cho and it starts to render weird no matter what model I use and settings and camera I use in that cho the same problem render happens. Just now I rendered the same frame using netrender but when I turned SSS on it rendered okay. Also there are wierd black lines when I turned on AO and SSS like in the picture. The lines don't stay at the same exact place and with the same shape but appears at random near the same approximate place each time and at varying sizes.
  4. Here's one: Only objects in the cho. It's random and it's hard to pin it down exactly. If I turned off other models when this happens and load a simple model it wil render the same wierd color. If it happens no matter what settings I use in the cho the same thing happens and I had to close A:M, reload the project and do a marquee render to test if it's okay. Also when I use the same project on netrender it will definitely render in wierd color most of the time.
  5. The error that kicked me out seem to went away for some reason... But now another problem came up. It seems that the thing that I mentioned about AM rendering the frame in in weird colors is true and it appears at random. Only one out of 5 tries turned out okay. I had to make a test render beforehand. And if I use netrender each and every frame will come out like this, regardless of the settings, even with no shadows no AO: I tried it with both v15 and v16 too, doesn't matter if I saved or reload the project and files in it's respective version. And this time I'm sure it's not my fault.
  6. Oh I got it. They're on by default n v15 onwards. Didn't notice that because v14 didn't have that feature before. Thanks.
  7. Now the aim at constraint for a camera in the choreography doesn't work. It does nothing when I applied the constraint. Tested with a fresh choreography and it doesn't work too. Any type of model or nulls doesn't work. Reloaded, resaved all available files and restarted the program and it doesn't work. Anyone has similar problems?
  8. Ya found it and it's fine now. Thanks!
  9. Errrr.... My TSM rigged model in MOST of my cho files aren't working in v15 and v16. They all work in v14 but a small percentage only works in v15 and v16. I selected my TSM2 rigged model in a cho and the control bones and the pose sliders aren't showing... Weird.... All of the mode buttons and mode related functions of the except for the choreography mode button doesn't work when I select the model. Even selecting any bones in the PWS tree of the model it's not showing. Resaved the cho file and the TSM2 rigged model in v16 and it didn't work... Anyone experienced this before?
  10. An update. Tried the last time and solved the phantom model problems. They're stuff between the tag in the model file. These are that contains multiple duplicate cache lines. So when the models loads it puts in a choreography tree. I rechecked it again and it was my mistake if selecting the cho. Easy to make a mistake since there are may versions of chos and models. It's like half past 1 am here and hadn't have enough sleep. Resaved them all with a with a "v16". So no proeblems anymore, for now. Thank you for the help.
  11. In A:M I just selected all the phantom folders and things that looked weird and hit delete and resaved under a new name. Never save new versions onto old filenames. Save all your old files so if something really odd happens it's easy to go back to when everything worked and compare and see what changed. Thank you for helping me out and thanks to everyone else too. I've opened the file in a script editor and there are alot of nested emptydrivers that are too confusing. I guess I just have to start over and copy paste all the keyframes of the models in the cho files since it would take less time I reckon than rummaging through codes. At least I've removed the modelshortcut parameters in the models. Nasty bug... About the v16. Anyone has any problems with weird athefacts when rendering? I had the same problem with v15 but it went away after I saved it in another copy and reloaded the project. But in v16 it didn't work. The models were all glowing in purplish green and stuff with random thick black lines. But when I reloaded the v15 version of the models they render fine. Anyone experience this?
  12. I'd open the model up in a text editor and first I'd look for something that looks like the problem When i opened your chor the model folders had just a "drivers" folder and two constraints in them. I'd look for model tags that have that in them. What did you delete in the cho file? I've deleted a bunch of Modelshortcut tag pointing to the shoe in two of the models that I had found to be the culprit. Then I loaded it into the cho file that you fixed. But this time (after I deleted shortcuts in two models like I said above) it loads withthout the shoes' name, and it can be deleted without kicking me out. So it's a little bit of progress. Before I deleted the shortcuts it would load dozens of phantom models with the name, and it A:M would kick me out if I try to delete it. About the SSS rendering the test scene using the A:M 15 it didn't give me problems, period and it passed a few passes. But I haven't try rendering it over a thousand pixels in WxH yet and higer number of passes yet. SSS is slower than in v14, but other render options are noticeably faster.
  13. I've got good news and a little bit of bad news. I've managed to borrow some money from my brother and sister to buy an A:M subscription. Now for the bad news. I've opened the file that you fixed and I've opened the models one by one and found the culprits. Two of them. So what do I have to do to see what's the problem with the model? I've removed the file from the cho and the problem of them duplicating didn't go away and the file is now over 1 mb.
  14. Sorry somehow in my second reply to you I said no but didn't notice that somehow it was missing when I edited it out. I've downloaded the cho and I'll get back to you. Thank you very much.
×
×
  • Create New...