Mash

Spoilers....

I would go down 1 of 2 routes here. First go for the FOV route, just select your camera, take a look at the focal length, then reduce the number. This will optically zoom out, giving you a wider field of view. If that doesn't work for you, then Add a second camera, place it inside the animated camera in the object list, activate this new camera, then navigate backwards in a straight line. The first animated camera will now drag the second camera around with it. Just be careful you dont back up into a wall.

The simplicity of a scene in this case will actually be working against you. On a complex scene, each cpu core picks a chunk of the image and spends time working on it before stitching it together. By rendering just a cube, the render buckets finish quickly and then move onto the next bucket more rapidly, increasing the chances of the error happening. For a similar example there have been problems recently with gpus cooking themselves when the game they're running is too simple. Instead of doing some heavy lifting on a complex scene at 4k and managing say 60 fps; they get to a blank loading screen, there's no geometry or textures to process and the fps suddenly ramps up to 9000 fps. Im simplifying here, but the bit of the card in charge of timing things can't cope with such a high frame rate and the gpu ends up blue screening or physically breaking. You have the cpu version of this. Your cube scene render buckets are getting processed so quickly, that it is showing up the instability of the timing part of the cpu that juggles the various threads.

Different tasks will be hitting your system physically in different ways. Your physics sims will be ramming 1 cpu core at 100%. Video editing will be hitting ram bandwidth, standard c4d renders will be loading up the FPU of the CPU across all cores. You can absolutely have a system that is stable for gaming and general system use which then falls over as soon as you start a c4d standard or gpu render. eg an overclocked gpu which fails during a game might manifest as a single pixel turning the wrong colour for a moment, but if it fails during a CUDA 3d render then it kills the entire app. Clock watchdog timing out is basically telling you that the cpu tripped over its own shoelaces whilst trying to juggle tasks across the cpu cores. This can happen if the chipset drivers arent installed and you just have the standard MS OS drivers, especially with newer high core count chips. Or it can be a more fundamental bios problem, again, most likely a newer cpu on an older motherboard bios. Or lets be honest, entirely likely overclocked too far. You havent said which cpu this is, but these days theres very little headroom for overclocking on most cpus and gpus. Most chips are already auto overclocking themselves under the guise of turbo boost anyway. Unless you have exotic cooling in your system, the heat generated will usually be your limiting factor even without overclocks.

Its just you. install latest chipset drivers update mobo bios ease off the overclock It will be one of these.

The project assets inspector and the render queue annoyingly use different code to check for missing files. The asset inspector checks for which files are genuinely needed to render the project, whilst the render queue just does a dumb check for the mention of a material. So, if you have a node in a material that isnt linked to anything, the project asset inspector will say "yeah, not connected to anything, dont worry about it" whilst the render queue shits its pants, throws up a red light and tells you the world is about to end. Options: - hunt down the unused nodes and delete them - change the c4d prefs to ignore render queue errors and just render anyway - search your hdd and just copy the offending files into /tex so the render queue shuts up

Material > illumination > Generate GI Strength

Just guessing here, but the support could just be free subscriptions as prizes, which essentially costs them nothing. Also, if youre going to spend money, spend it on people you want to become your customers, not people who already are.

You can, but don't. You should virtually never export h264 video from directly from c4d. If you spend 5 hours rendering, but the compression is too high or too low, then you're 100% screwed and will need to render the entire thing all over again. Continue doing exactly what you were already doing, render an image sequence (png is the simplest option without getting into the details) And then use premiere or after effects if you need to do work to it (editing, colour correction etc) or go straight into adobe media encoder. The quickest option is media encoder. Select File > Add source. Click the first image of your sequence and make sure the "file sequence" checkbox is enabled. You will then see the preset should default to "match source - high bitrate" Play around with exporting to high, medium and low to get a feel for how the file size vs quality changes and use whatever works best on the website If you want to use premiere; make a new project then select File > import and click on the first frame of your image sequence. You will see a small "image sequence" checkbox below, tick this. Now right click this imported thumbnail and select "new sequence from clip". Lastly you can export the video: File > Export media, use the presets called "Match source..." and select high medium or low as a starting point. If none of these is what youre after in terms of file size, you can come back, unfold the video settings and adjust the target bitrate then re-export.

Thats 99% likely the picture viewer cache. It should empty after you close the app, so maybe you had a crash. If you open your prefs and go to the memory section, you can see the path and the max file size. Basically youre safe to delete them

You think a client is going to maliciously upload your demo reel to get revenge for a high quote?.... jesus, remind me to never work with your clients.

I just go down the route of "its easier to ask forgiveness than permission" If you ask almost any entity for permission, they'll almost always just say no, because there's nothing in it for them and just potential downsides, so they will say no almost every time. In reality they don't care, and if you include it, it wouldn't be worth their time to do anything about it. The realistic worst case scenario is they find it by chance and ask you to remove it, in which case just remove it and reupload the reel without that part. It also depends a bit on what you do with the reel. Personally I've only ever sent a private link to people when needed, so the video isn't out in the public for anyone to see, this makes the odds of anyone important noticing it more or less zero. Honestly, your main concern should just be "is this going to piss off a client I want to worth with again"

Fields and mograph effectors would be a good example. they take the OM as the central place to view inter-object links and largely throw them away so now theres links, but no way to see where they are unless you start clicking through very object to find them.

I think people are just being realistic. LW needed a complete top to bottom overhaul 20 years ago, they started to do this but the task was so huge that it pretty much killed off the app. They more or less gave in, went back to much of the old code base and never fixed the fundamental flaws the software has since its Amiga days. The rewrite was such a problem that all the programmers left and formed their own company where they would do the rewrite in the form of Modo. C4D did a rewrite for R6 back in the late 90's, this damn near bankrupted the company. They have been doing another rewrite for what, 10 years now? Only now are the fruits of that labour starting to actually show for the end users. Taking LW's ancient code and fixing it is a mission only a lunatic would take on. So their only real option is to make a spiritual successor to LW from scratch.... but isnt that just Modo?... And if its just people doing it for the love of the software.... isn't that just Blender? My thoughts can best be summed up as:

I'm personally still waiting for the new Commodore, Escom, Gateway2000, AmigaInc, Cloanto Amiga to run it on.

Actually, one more anecdote. I used to do corporate training too, mostly a 50/50 split of a single company hiring me to teach 1-5 members of staff or a training centre doing mixed open classes of up to 8 people. Either way, people would pay around £200 per person per day for these classes. These are 99% fine, no problem. What I also did though maybe once or twice a year was work for a training company that did EU-funded training sessions to update people's skills, mostly people getting into 3d for the first time coming from PS / AE or the occasional lightwave refugee. The difference here though is that they were 100% funded by some EU agency, so people could attend this course for free. All they had to do was sign up, pick a day, then turn up for a few days for completely free training. It was a shit show. The classroom had 12 workstations, every class was fully booked. At absolute best they would get 3-4 people turn up, with the other 8-9 workstations just being no-shows. People would turn up for the first day of the class, then not turn up for the other 3. People would miss the first 3 days, turn up for the last day, and expect to be caught up on the stuff they missed. People would bring in a project, and expect that I was going to just sit there and literally do the project for them; "i'll watch, thats how I learn" Oh and a final facepalm; being a giant EU funded money pit, they pissed your tax money up the wall in the most spectacular fashion. The workstation setup was absurd, every desk had dual 30" 16:10 apple monitors on it. I couldn't bloody see anyone for the entire course. Plus, did they grab a cheap/free educational licence of the software? Nope, all 12 machines had full commercial perpetual licences on them. After about 4 sessions of this I told them not to call me again. If you give away something of value, you'll just get piss-takers, time wasters and entitled people.

Giving it away for free to deadbeats is what got him inundated with crappy messages. If you make a product and sell it, then the people you'll end up communicating with are more professional users. If you give it away for free then go check out reddit.com/r/choosingbeggars to see what kind of idiots you'll attract. We sold 10's of thousands of training videos, over the 15 or so years we had something like 80% of emails just to say thanks for making the video, 20% asking for help on a project they were making from the video and I think to the best of my knowledge we had like 2 complaints ever; 1 DVD got lost in the mail and the other was someone complaining his internet was too slow to download the video without timing out. Flip to our youtube channel for free stuff and we have message after message... Why haven't you updated this video to the latest version I know a better way to do the effect than you I can do this better in blender You breath too heavy I dont like the sound your lips make by the microphone You speak too slowly You go too fast .... Give something away for £0 and the value of the feedback you get will also be £0 Heck, go sell it to insydium and cash out. Never have to deal with another customer ever again

Its a shame its gone. Its a shame people are dicks. But the guy completely dropped the ball on making the most of what he has. He makes an incredibly good, useful, valued tool that people want and use.... doesn't charge a penny for it, then complains he has no money and that high profile people are using it? ConfusedJackieChanMeme.jpg Add some more shapes, polish it off AND CHARGE MONEY FOR IT!. Advertise it, "As used on star trek discovery!", Sell premade texture packs for the ultra lazy. The mind boggles how you can hold a golden egg in your hand and do nothing with it.

When every single programmer leaves an application, that's the death knell, there's no coming back from that. I loved the competitive nature of c4d vs lw vying for the top underdog status against maya and max, especially the over the top lw fanboys who would defend every fault the application had. But its been dead in the water for (checks calendar) 20 years now. Short of a miracle, it ain't coming back. For me, lightwave is up there in the hallowed halls of awesome software of time gone by along with Amiga's workbench OS, Softimage, paintshop pro and DPaint. But lets face it, its dead, no new owner is ever going to manage to catch up to where the competition is.

If you cant do the basics, then how does that make it much more capable than c4d's system? The only shortcomings of c4ds take system from my experience is occasional bugginess (deleting a take can remove unrelated take data), confusing names for tools (lock overrides, wut?) and poor animation support.

Light the scene? If you stick a product in a white room with white lights, its going to look pretty dull.

Make 1-20 random greyscale values, this will take you seconds. then right click the gradient and keep hitting "double knots" to multiply how many are there. then finish with a right click and "distribute knots" to evenly spread them out.

The answer is always, it depends how close youre going to get. it depends how well lit the shot will be, it depends what res youre rendering to. For a generic object in a room, I would take a gradient, set it to circular, then throw in a ton of random greyscale values to make random concentric rings. then either bump, material displace, or displace deformer. Then smush it a bit with an ffd for the imperfections. Then final noise bump over the top for undulations

100000% yes for every reason under the sun. You're rendering to an mp4 video, theres a crash or powercut... all your rendering is lost in a corrupt mp4 file You render for hours or days, then realise the compression is too high and the image quality is ruined You render for days, then realise c4d is 1-2 frames lagged with its animation as the movement happens after the audio hits, so the entire video looks out of sync Basically, unless its a quick 5 minute test render, always render to image sequences, virtually no exceptions.

Object mode is probably what you want 99% of the time. Unfortunately c4d's first person "camera" mode tends to get stuck when zooming so I've personally mostly written it off. You can fix it for a while by hovering your mouse over an object in front of you and pressing the insert key twice, but after a while it just gets stuck again.