Friday, December 18, 2020

Twilight at the old sanctum


Now we're cooking. So many experiments in this one render -- and they all worked out. This is Michael 8 standing in DM's Abiding Sanctum, with Iray lights set, and Iray creating the sky (iue., "Draw Dome" is turned on). I've also changed the shaders on the costume; the DOF is set on the camera ... and the whole whole thing rendered in six minutes while the computer stayed cool as a cucumber!

I'm juuust about through the experimental phase, in many ways. Everything is working just fine, and I've also thrashed out how to get the third party content to install properly, and (just as important!) be FOUND after it's installed! Turns out, it's the SAME file path to install both DAZ Studio Content and Poser Content. Studio reads the content differently and pushes it into two different menus, when you come to load it into scenes (which I wish it didn't), but during installation, it's the same file path. So we're happy here.



Next, I'll be installing lots and lots of third party content (something like 250 items), and then ... we're good to go. This is juuust starting to turn (back) into real fun! 

Saturday, December 12, 2020

Installing third party shaders in DAZ Studio 4.14 ... done!

One thing at a time! I wanted to be sure all the old Studio content has installed properly, so -- can we get Victoria 4.2 to load properly, and render nicely? Answer --


-- yes. That's Victoria 4.2 rendered in Iray, with one of the old costumes given a makeover with Iray shaders, Not bad. In fact, the low-poly models render FAST; just keep in mind that when you get very, very close to them, Iray shows up all the cockroaches. You will see polygons, if you get too close! So keep these figures for background scenes, presumably.



The next question was, since the old 3Delight render engine is exactly that, old, does that mean simpler renders -- raytrace! -- will go fast, because they're not Iray renders? Answer -- a resounding no! Not only do raytraces take about 4x longer than Iray renders, when you see the results side by side, they're disappointing...


 That's still just the old low-poly Michael 4, wearing Neftis's Mon Chevalier hair (which is a Poser prop), and Xurge3D's Mediaeval Royalty costume (also optimized for Poser). So the surfaces had to be adjusted for Iray, which turned out to be tricky but far from impossible. The thing is that M4 renders up quite nicely in Iray ... in four minutes. The raytrace is cartoonish, and was at least 20 minutes, even with The Hulk running "high and hot." Hmm.


I rather think I'll be sticking to Iray from here on out. So that's another question answered. Next: how in the hell do you install all your Renderosity content into Studio 4.14, under Windows 10? I knew the answer to this for Studio 3 and Windows 7, but this is very, very different. Well, one step at a time. I installed a pile of shaders first, and it turns out, they work just fine. So far I've applied them to many props, costumes and so forth, and they look a treat:

I did the ground, the column and so forth, in shaders to make the simple old props look good. This little scene here has 10 props and four lights ... I think I've got the photometric lights worked out (bear with me; I'll write about this as we go, when I'm sure). Right now, the only thing I can pass along with confidence is the answer to this:



Where do you put third party shaders from Renderosity into DAZ Studio 4.14, to have they work properly?



Here's the file path:



C:\DAZ 3D\Applications\Data\DAZ 3D\My DAZ 3D Library\Runtime --



After which, copy shader sets (or packs) into Runtime\Iray or Runtime\Shader Presets.



It gets more complex if you're installing props, because you need to know if the assets you're installing are DAZ 3D format, or Poser format. In the case of the Xurge3D (Poser) costume Michael 4 is wearing here, I've got it to work, but I want to check the installation process a couple more times before I quote you exact addresses. It can be bloody confusing!



More experiments to come. I need to thrash out a lot of questions about lighting, and then I need to install about 500 Renderosity items, from shaders to lights to poses to hair to costumes and props. This will take a wee while. Patience! 

Thursday, December 10, 2020

So, does Michael 4 work in Iray?

 


Michael 4 in Iray; costume by Xurge3D



The short answer is -- yes, Michael 4 does work in Iray ... it just takes a bit of nipping and tucking! The top image is the Genesis 8 figure, Michael 8, with all materials, textures, surfaces designed for Iray -- it's plug and play, just click everything into place and hit render. This took about eight minutes (!), and I'm fairly happy with it. (The lights are unimaginative, but they're not the focus of the experiment. Time to get fancy with Michael 8 as we go along.)


But about 95% of everything I have is designed for the old raytrace engine; it's thousands of bucks worth of stuff ... surely there has to be a way to save it? I can't actually afford to buy everything again! So the question uppermost in my mind as always been, "Does Michael 4 work in Iray?"

Here's the answer to that! If you can configure the materials, surfaces, textures, the old low-poly models render up very nicely indeed. They don't have the "oomph" factor of the Genesis figures -- but they also render in a tenth of the time! Not too bad at all...

I've worked out how to install shaders and Poser content, and third party content to DAZ Studio 4.14 in Windows 10 -- and I'll share the details in my next post. I'll also share how to fix the surfaces to get Iray to render the old models nicely. So far, so good!  

Friday, December 4, 2020

In at the deep end! First render off the new computer

 


Okay ... the oars are at least dipping into the water LOL! First render off the new computer, first glimmering of mastery over this version of Studio. The challenge was to FIND everything, which is far from easy, as yet. Then to configure everything (ack). Then to get the DOF figured out. No problem there. Am still faffing on with the lighting, but I'm about halfway through the process. Don't get too excited yet: almost everything you see here is a preset, just arranged and configured.



The only real fly in the ointment today was trying to get Affinity Photo to play nice, and it refused; and finding out that my Wacom Bamboo will need to be re-re-reconfigured for the new computer; as it stands, it just doesn't work, and/or is pure torture.



So ... first render. The Genesis 8 "Rex" character, plus shirt, plus hair, plus a shader on the shirt, and a necklace; add a set, add a backdrop, suitably blurred to match the DOF; add lights. Render --


Results? This hairstyle never would render on my old computer. The GPU "choked" before it was finished, at about the two hour mark. This was the work of about four minutes flat, rendered at 2000 pixels wide, and middle-high quality. Smiling there! 



I needed to paint part of the shirt for "poke through" that couldn't be fixed prior to rendering, and if I'd been able to do it in Affinity Photo, I'd have been delighted with today. Nope. Had to start up the old system, and used Photoshop as a tide-over. These problems will be addressed tomorrow, when I'm not so tired!



All in all, I'm quite happy with this as a first experiment. Lots and LOTS of problems to iron out, but now we're on our way! 

Thursday, December 3, 2020

The Hulk has landed!

Eventually, the day had to arrive. HAPPY NEW COMPUTER! It's been a year since I turned off my old sesktop before I fried it; I haven't even tried to do art in that time -- therefore, the old machine still works, and will stay right here it is. And the new machine, designated "Hulk" on the LAN, is here some weeks early (thank you, Dave!) ...



It's humongous. Also whisper quiet and running cold even i the hot weather since summer began. Look at the size of the main cooling fan; there are two more in there. Whooooo!!! 😁😁😁 Dave hooked it up for me (saves my back and knees the hurt of climbing around under the desk; and I appreciate this muchly) ... and I took over, to install software. It's my Christmas present, of course. Happy, happy, joy, joy!

For those who are into the hardware side of things, here are its specs:

  • AMD Ryzen 9 3900XT, 
  • 12 cores threaded as 24; 4.7Gh; 70MB cache. 
  • B450 Tomahawk motherboard (MAX AM4); 
  • 16GB of RAM (Thermaltake ToughRam Z-ONE RGB, DDR4 3200Hz, CL16 Memory). 
  • Hard drives: SSD, Samsung 970 EVO 1GB boot + 2GB internal. 
  • GPU: the MSI GeForce RTX 2070 Super Ventus GP OC Edition, 8BG, with another dedicated cooling fan (Thermaltake Pure 140mm). 
  • Bluetooth 5.0 (NIC Herald).
  • Power source: Thermaltake -- Suppressor F31, with its own big cooling fan. 
  • 8 USB ports, half of them USB3, one USB C, plus ethernet, 4x speaker-line outs etc.,
  • Win10 64. 
  • "Water cooling ready;" and we can double the capacity of the GPU and RAM, if needed

Sooo, the first thing was to "migrate" from one machine to the other...


A couple of days saw me slogging through the job of installing miles of software.Word 2016, Affinity Publisher, Affinity Photo, Krita and Irfanview were all quickly on, though I needed to import about 750 fonts, plus 4,500 brushes to the photo and paint programs, from my old system. Turned out to be easy. Next came Amberlight (on and tested) ... then, when everything was set, I got into the big stuff, for which The Hulk was built (by IT Warehouse at Marion).

First bit of bad news along this road: Bryce 7 Pro is a 32 bit program only, so it will not run on The Hulk. End of statement there; and all the more reason to keep the old computer on and working (it's a Windows 7 machine, 32 bit, and though Bryce stresses it, it will run okay).

DAZ Studio was an all-day install job, to get the new version (4.14) plus enough "assets" to get my oars back in the water. Done. Then, start up DAZ and ... urk. Talk about a learning curve! The interface has changed significantly from the 4.11 I was accustomed to; and I've simply forgotten a lot. I have to relearn some things I used to do automatically. Also, Studio is simply not cooperating in one or two ways, though I'm sure there's either a solution or a work-around. I'll get there; I;m just not quite there yet! 

I also have to manually install many hundreds of third-party assets, from Renderosity and various other 3D marketplaces. That will be a loooong job, so I'll do it a bit at a time. Not a problem, just a chore.

First bit of fabulous news: the unbeatable "file save error" I was getting on the old system right throughout 2018 and 2019 has not, repeat not, recurred in Studio 4.14 under Win10. I can now build a project, save it, reopen it, and have everything right where it should be.

The downside? I can't seem to get raytracing to work! This is terminally weird, and I'll be working on the issue. It's way beyond odd. But that's my problem, and I'm on it, albeit slowly.  

Can't wait to see how this system handles the workflow. I'm hoping that what took three hours last year will take twenty minutes now. At the moment, everything is working fine, and the system is dazzlingly fast; I just have to climb halfway up the learning curve before I have pictures to upload here; and I'm thinking that I might blog my progress in Studio 4.14,  just as I blogged my baby steps, 11 years ago, in Studio 3! Stay tuned, and bear with me. At the same time as all of this, I'm editing a novel, and while it's not actually difficult, it just guzzles time. Eats up your day and pushes art to the sideline. Done by Christmas, though, and then ... art!!  

Friday, May 15, 2020

Halfway to that new computer, and counting down...




Yes I know -- these are re-posts of art done six and seven months ago! You don't have to tell me about the time that's going by ... in fact, we're halfway to the new computer that will mean I can get everything installed and working perfectly (theoretically, at least. I realize there will be issues -- there always are). The last few "touching base" posts have involved photos, but I wanted to post art today, since this is an art blog, after all. I literally cannot squeeze art out of the of the old desktop without risking its life, so the only option is ... re-post some of the nicest stuff I did in 2019, when I picked up the threads and ran with them.





In case you're wondering ... well, my brain is full of ideas. I can SEE the images I want to render; but there is no way I can create them. Not with the existing video card. On the plus side, we're in mid-May now and cruising down the other side of the year to Christmas.

What am I doing with my time, since I can't do art? A lot of blogging (I have three blogs; this one, plus travel and personal, and am considering doing a photo blog). But mostly, I'm writing. A second novel is already done, a third is in the works and half done at this time. Four of my short stories have been published in the SF and Fantasy press in the last year or two, and one is being reprinted. Next year, when the pandemic is done (please gods, it will be done), I'll be on the trail of literary agency representation; and if the books are as promising as I think they are ... well, now.

At the moment, though, art-wise, we're just marking time. Best I can do is keep the images in mind and then slide back into art with a computer that can do the work easily, and do it well.

Saturday, April 25, 2020

What went wrong?! (And how to fix it)




To most efficiently answer a question just asked, I’m going to tackle it in a new post. First: relax, take a deep breath! The most common question in photography is, “What went wrong?” And it’s been that way since the first photograph ever taken.

Numerous things can go wrong, but the simplest of all (and trust me, we all do it sooner or later) is where you forget to reset the camera after that special job you did two days ago … your images are consequently rubbishy, and perhaps you had no chance of taking them again. The camera remembers the last settings you tapped/dialed in, and if you have a scatterbrained moment you’ll end up with something just plain sad. (You can also find yourself shooting into the sun to get any photo at all, which won’t produce a good image; or the day can be so overcast, your pictures are almost monochrome, flat dull and boring. See below.) So ―

The question actually was, “How do you rescue photos that went wrong?”

Well, it does depend on *how* the photo went wrong. If it’s out of focus, you’re mostly out of luck. If it’s blurred by camera shake, the same (prevention is better than cure here). But if shots are just way too dark, or too washed-out pale and colorless, so long as they’re not blurry, you can do a lot with them.

The ultimate dull day photo! What can you do with it?
(Disclaimer: dull-day photos can have a tendency to be “soft” too, even if they’re in focus. They can look mushy, even if you held the camera steady. The “mush” effect is down to the camera’s aperture being too large Without getting technical ― big aperture = soft picture. Small aperture = sharp picture. It’s a *lot* more complex than this, but that’s the first rule to bear in mind. The only way to get a small aperture on a dull day, without trading off for a loooong shutter speed and risking blur from camera-shake, is to increase your ISO setting. Any halfway decent camera has this function … the instruction booklet is your friend. Generally speaking, the lower the light, the higher the ISO you want. Higher ISO settings mean the camera gathers and records more light, so you can have reasonable shutter speeds as well as acceptable apertures, even if conditions are dim … theoretically. The more automatic the camera, the more it’ll take you along for a ride, so you’ll always need to be careful. End of disclaimer!)

Back to original question: for the moment, forget about why the picture is under- or over-exposed and looks like crap. Can it be saved, and if so, how?

I can’t give you a how-to for your specific camera or software, because they’re all different. But I can point you at a free program that’s a godsend for working with iffy images and turning out lovely results in a fraction the time of mucking about in Photoshop. Go to irfanview.com and get the latest version. I’ve used this for ten years, and I swear by it. For my purposes, it’s the best thing ever. Now…

When a photo is too dark, too pale, or has no color, how do we save it?

Let’s work with one that’s washed-out pale and colorless (because that’s what I have to hand). Open it in the program. First, before you do anything, use your eyes. Just LOOK at it. See exactly what’s wrong with it.

An old grumble about digital images is they can be harsh, hard, too contrasty, with no information recorded in white areas, and dark zones crushed straight to black. Within the two problem areas (blank whites, dead blacks) there’s an amazing range of possibility. You’ll have to trust your own eyes to know when you’ve achieved what you want, and the good news is that even thoroughly lousy photos usually have a wealth of “information” hidden in them, which you can reveal by jiggling the settings. Have a look at this, for example:

See at full size, please. My word of honor: it's the same shot, before & after!
You might be tempted to pounce right on the “Brightness” setting, because it’s the word you best understand (what’s this Gamma thing, anyway?) but ― please don’t. Brightness is the setting you want to resort to last, if at all. Brightness will affect the whole image, meaning dark areas, mid-tones and highlights all get lighter or darker together, which is almost certainly not what you want. Gamma, on the other hand, controls the “ratio” between dark zones and bright zones. The easiest way to understand how this works is to use it, do it, and see it work. It’ll start to make sense as you play. But ―

Before you get into fiddling with the Gamma, take a long, hard look at your image. Is it harsh, is it contrasty? Digital pictures so often are, it’s actually worth having a quick mess about with the Contrast setting, just to see how it improves the picture, in concert with Gamma correction. Eight chances in ten, it will.

Because digital pictures tend to be contrasty, you want to flatten the contrast. From a default value of 0, drag the slider left till the image looks unpleasantly dull. It probably looks far worse than when you started … but if you study it closely, you’ll almost certainly see that “information” has become visible in both the bright and dark areas, detail you couldn’t see before. Aha! Now you’ve got information showing up, the next step is to improve the ratio (!) of dark to light areas, to recover the lovely tonal balance an image should have. This is what Gamma does.

From a default value of 1.00, drag the slider left (Gamma down) or right (increase Gamma), till the picture looks good to you. Everyone’s preference and eyesight (not to mention, monitor settings) are different; you’ll have to decide what’s right for you. When you’re happy, sit back and look at it. Looking good? Think it might be better?

Please view at full size...
We all tend to judge our pictures against shots we see in magazines and brochures, and by and large these are color-saturated, sometimes even over-saturated. It’s worth at least trying this out, so see if Color does improve your image, before you call it good and save it. You can always undo, if it makes a mess. From a default value of 0, drag the slider right until the color is too vivid, then pull it back till it looks just right for this picture.


In Irfanview, you can also muck about with the R,G,B values (Red, Green Blue) of an image; but you will probably be appalled at the results if you start fiddling with these. It takes a lot of practice to use this efficiently, and it can be a world of frustration. My advice would be, in the early days, leave them alone unless you’re actually wanting whacked-out results! In due course, play with them … learn as you go. Have fun.

TIP: if your image has red areas, keep an eye on them. If you overdrive the color, your reds will become blocks of color without any “information” inside. This is your clue that you’ve dialed up too much color. Dial it down again till the reds contain information, and you know what this image will naturally tolerate. (If you want to go beyond this, you’ll need to be working in layers, which puts you in Photoshop, GIMP, Krita, Affinity Photo, and so forth; and that’s far too technical for the average user, so we won’t go there today. But for reference, Irfanview, Krita and GIMP are free; this doesn’t have to cost you an arm and a leg.)

By the time I was finished rescuing my photo of autumn vineyards just outside Willunga, I’d flattened my contrast by -26, flattened my Gamma to 0.51, and poured a lot of color into it … +128. These are not instructions: every single image is different! I can’t tell you what numbers to type in.

If the image you’re trying to save is way too dark, basically, do the opposite of everything that’s been said here, LOL. I don’t have any blackout images to hand, so I’ve used a washed out image, (yes, the sad result of forgetting to reset the camera. I did reset it ― retook the images from a slightly different spot, and only when I got home did I discover the phone line running right through the sky of the correctly-exposed pictures, spoiling them. The pesky phone line drove me back to the pictures with the incorrect exposure, and the result? Nice).

Hope this helps!

Wednesday, April 15, 2020

Touching base with pretty things





Touching base in April with images -- not specifically art, but straddling that line where photography and art merge, one into the other. Why? Because my big PC (which handles the 3D art programs) is staggering, and if I try for a long render, it'll croak! Also, it's permanently offline with an uncooperative modem. And I can't get a new system till Christmas! So 3D adventures will just have to wait ... but I do want to touch base at least once a month, keep this blog juuust ticking over, and say hi to everyone, especially when we're all locked down so tight, I know a lot of people are increasingly bored out of their collective gourd! So...





The big news for me personally is that I took the plunge and bought a new camera in February. The bummer deal (and that is putting it mildly) for the whole world is that by the end of March the pandemic was hitting everyone, everywhere; and as a result, I can't take the new camera anywhere until about September! To set your mind at rest --

Dave, Mike and I are in the safest place in the world, in South Australia. This state is starting to see days with zero new cases reported ... SA was able, via stringent measures and public cooperation, to hold the number of cases reported locally to very low numbers (in a state of 1.7m people, most of whom live in the metropolitan area, only 433 people have tested positive by the time we start to see our "zero days." Never more than twenty people, maximum, were hospitalized at one time, and I believe the most people at one time in ICU was six, (possibly seven). There have been four  -- yes, just 4 -- fatalities in this state, but my information is that each them was literally too sick to be rescued after contracting the virus overseas, most often on a cruise ship. One's heart goes out to the families of those four grandparents who, tragically, came home to die ... at the same time, one applauds SA, where -- at least to this point -- no one actually who fell sick here has perished, because medical care is top-notch, free, and fast. At this time, I'm extremely proud to be a South Aussie.





So, where are we at this moment? In lockdown, yes; in self imposed exile ... not taking the new camera anywhere -- being good and "staying home." But in the few expeditions where I had the opportunity to field test it, I was impressed: Leica lens elements, 20.3MP, 1,005mm zoom, far better "register" than any of the Fuji cameras, which all gave very harsh images. I'm loving my Lumix TX90 and -- well, roll on September, when the lockdown lifts and we can go places! We'll be visiting Mount Gambier, Clare Valley ... lots of places. Having said that, at this moment we're all well, and working hard. I'm writing. I've sold four short stories to SF and fantasy magazines, and am working on a second novel. Am also looking forward to the end of the year, and that new desktop PC with the "oomph" to run the demanding imaging programs, but till then...





...well, till then I'll touch base now and then, either with photos or art, even if the art is reposted ... or perhaps a review of an artist, or art book? However it works out, Christmas will be upon us before you know it. Someone said not to long ago, "Once you get past Easter, the rest of the year goes like a shot." Uh huh. Easter was last weekend, and I spent the four-day "break" (a misnomer, because when you're in lockdown there's nothing to take a break from; and Dave had shifts right through Easter) transferring hundreds of Gigs of data to and fro between drives. Now I have access to every digital shot I've ever taken, back to the first 1MP Kodak camera we ever had, in something like 2001. So with every image at my fingertips...





--suffice to say, there's no shortage of images to share! And there is a line where art and photography blur, one into the other. I like to think that I'm riding that line a lot of the time. And yes, this year, like a kid, I'm waiting for Christmas! There will be a post called "Happy New Computer" at some point! Then I'll spend a few days getting everything installed, and we'll get back to 3D art. The wonderful world of Iray. Till then -- have some more photographic eye candy here.

See you in May! (Or perhaps sooner, if some of the art ideas in my imagination that don't involve long renders bear fruit...)