Jump to content


Regular Member
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Poor

About Dannyx

  • Birthday 01/13/1994

Profile Information

  • First Name
  • Last Name
  • C4D Ver
    19.053 Studio
  • Location
  • Interests
    Computers, electronics, cars
  1. Good day folks. I recently switched over to C4d 19 hoping it would run smoother and improve things, as my rig is not particularly powerful. The only thing that stands out the most is the R9 390 graphics card it's got. So far, the program itself does seem to run smoother and doesn't lag too much in the viewport, which is where I had the most issues, so I'm pleased with the overall change so far, but it's the rendering speed I'm ultimately hoping to improve. As a complete novice who's doing all this for fun, under no pressure and without any obligations, I don't usually read up or do research on these things: I just dive right in, clicking on stuff and messing around until I get what I want - an occasional crash is thus also to be expected. I'm currently facing an issue with an old project which was made under R15. To cut the story short, switching from the "standard" renderer to ProRender is not as easy as I had hoped. It's not something that you just select and it "runs in the background" doing stuff for you - I had hoped it would simply "transfer" the workload from the CPU to the GPU (which it does, no doubt), which is something I really felt the need for, given the aforementioned not-quite-up-to-the-task system. Sure, there's a LOT ! more to it than that (tons of settings to mess with), which I quickly discovered the hard way: when I went to "ProRender" in the viewport and clicked "Start ProRender", the whole viewport went completely black...I must be doing something wrong, since I can't even see the textures which have "luminance" enabled and those should be visible even in total "darkness". Should I stick to "Standard", or push on with ProRender ? I know the answer heavily depends on the scene. It's animated for one thing. Can I expect ProRender to decrease render time, or will it be roughly the same, just in a different "method" ? The subject of ProRender is huge...
  2. I use the player that K-lite comes bundled with for day-to-day media tasks. Codec's probably the issue. Not sure if K-lite affects anything though. I got it mainly because I often need to play unusual formats that windows doesn't support natively.
  3. Neither, because the AVI files do not load at all - it says invalid file format. I got Klite codecs installed and I'm able to play every format known to man, but C4D doesn't load AVIs. Try loading any AVI file and see if it works for you.
  4. Good day folks. Wanting to benefit from my slightly more potent GPU, having a relatively slow and weak CPU, I upgraded to R19 from R15. While it does run smoother and I love it, there's one rather important issue: none of my "video" textures work anymore when I load the project I was working on...in R15 they work perfectly and I can confirm this because I have them installed side by side on the same PC. Has support been removed for these ? They're the same AVIs and the same project, so what could the issue be ? Doing it with an image sequence seems daunting and space-consuming, so I loved the ability to import video straight in. Am I doing something wrong ? Quicktime is installed, though R15 worked fine with AVIs even before I installed it. I always disliked upgrades removing useful features and this is no exception :( EDIT: You know what the really crazy thing is: in R15 I was unable to import MP4s...ok, fair enough, I converted them to AVIs which worked. Now in R19, I AM able to load MP4s, but NOT AVIs...how's that for a total troll ? :))
  5. Area light making scene turn white

    Switched over to "Area" shadow just to see what happens (again, I'm a beginner at this stuff and have no idea what most of these setting do by name...practice, practice, practice...), and I haven't noticed anything "off" so far. Still looks OK and hey, no more white stuff :) It sometimes went away after disabling and re-enabling the light object itself - I just remembered that's how I tricked it into playing along. EDIT: VERY slow with area shadows - I rushed into typing the reply without waiting for the whole frame to render and I noticed it was still going...
  6. Good day folks. I just came back to a project I had been working on for a long time now, being a beginner and all and it's done now and ready to render, but I've ran into an issue, which it HAS done before but never actually found a cure: sometimes, and this is the key word here, SOMETIMES when I do a render, the scene comes out all white, like a very bright light is overtaking everything...other time it's fine. It seems to be totally random: sometimes I exit the program, launch the scene again and it's fine. Other times I have to restart the computer and it's fine, other time neither of these work. I tracked it down to a light causing this: it's a white area light set to "shadow maps" and sure enough, when I hit "render", the status bar says "rendering shadow maps". Takes about 30s, my rig not being really up to the task of running C4D, but we make due with what we have. If I disable this particular light, no problem: instant rendering (no more "rendering SM" message) and the colors and tones all look like they should. Trouble is I kinda need this light to make things look good, so I can't just delete it. There are other lights in my project and they too are set to "Shadow maps soft", so what's special about this one causing the scene to mess up ? Another aspect that might be of interest is cloning: I'm cloning this light to create several ceiling-type lamps sort-of deals - will probably get a lot of hate for breaking some taboo C4D rule about cloning lights :)) It did this a couple of times when I was building the scene too, but I overlooked it thinking it would go away before the final render, but it doesn't - at least not always. GI is not ticked in render settings - looks very good WITH it, but the time it takes to render is very long for my PC, so I dropped it. It's not related to this, since I tried it both with and without it and the results are equally as sporadic... What would (generally) cause this ?
  7. Making textures change randomly

    Ok guys, update: I installed quicktime and now upon loading an MP4 file, the frame counters do show up (they're no longer 0) but the video's still black...
  8. Making textures change randomly

    I'll probably go down the easy route, which is composing the video in an external editor and loading it pre-made for the sake of time, but for the sake of learning and building skills, I might come back to it at some point, no doubt about it...not really on a deadline or anything - it's just for my own personal entertainment - though it would be nice if it didn't take all year either :))
  9. Making textures change randomly

    Well someone suggested I'd use Xpresso and I figured I'd look into it. Didn't look too deep though, like I said. I thought perhaps it could randomly switch between a video, static (perhaps a video file also) and maybe other videos too (like the TVs changing channels), since I ASSUME it's just a matter of getting it going and then you can tell it to mess around with as many textures as possible.
  10. Making textures change randomly

    MP4 is what most of my files are in so it's mostly a convenience thing...yeah, they can be converted no doubt, but I reckon that would fill a folder with an image for each individual frame which would be very large...is this true ? I was thinking of doing it in post indeed, but I'm not sure how I'd go about telling my editor to replace just that one portion of the screen, since the scene is "moving", so the screens of the TVs will always be in a different place....powerful editors can probably do tracking and stuff, but I don't think I'm up to the challenge of learning a new editor just for 20 seconds of intro :)) Had a look at Xpresso to at least get an idea of what it does - it can get extremely complicated, but I got the general idea: a parameter changes others. How would this apply to textures though ? I saw the guy using it for sizes and stuff...
  11. Making textures change randomly

    Not really in a hurry but not entirely dependent on this one effect either. I could just keyframe an occasional texture change...at least I think it can be done - I saw the little keyframe dot near the texture file entry (you hold CTRL and click on it to add it to the timeline), so I'm guessing it would be possible to do it the hard way. It's only a few seconds (around 10, if not less), so no need to complicate things too much. The rig is fairly slow for this kind of work, so rendering might be an issue as well....
  12. Making textures change randomly

    I don't have quicktime installed ATM indeed, so I'll give it a go. That's most likely it....strange - I thought it was because of the codecs or something, despite having K-lite installed, which was all the more annoying since I'm able to play back all the formats on the planet on the PC but not load MP4s in C4D :))
  13. Making textures change randomly

    That's basically what I wanted, though it's still not done native in C4D I reckon. Still, I'm having trouble getting MP4s to work...
  14. Making textures change randomly

    Doesn't C4D accept MP4s as textures ? I saw a tutorial where it worked, but all I get is a black texture and 0 frames...AVIs work just fine :|