Said with a huge smile.
ACDSee Classic (or V3.1) became a victim of what's called 'feature creep'. If you used it then you remember how stunningly and blindingly fast it was at opening images. It didn't fix red eye, or have anything but the most rudimentary image manipulation tools, it just opened pictures. It was simple and straight forward and Wham! Bam! Thank You Ma'am Fast! This made it a huge favourite with us early professionals in the graphics industry. In my lab we were scanning 9 inch negatives from aerial surveillance film (15 minutes a scan) and ACDSee was the only program besides Photoshop that could open the images, and it did it in mere seconds. It also did bulk renaming, that was a deity send. One of the best loved features was the ability to select images with ctrl-click, hit the 'eye's icon for full screen and scroll through them with the scroll wheel. The one-handed crowd loved that wink, wink I appreciated the fact that it was also Canadian (Bob stands on a beaver dam and waves his little Maple leaf).
(Cue ominous music)....then it started. Subsequent versions began adding features that slowed it down. Each new release got bigger and s-l-o-w-e-r. We complained bitterly. Oh how we bitched. But it was to no avail. The drain dead, myopic marketing punks had decreed that more was better. Computers got more powerful, negating some of the speed loses but images also got bigger. Version 3.1 was available for quite awhile and was renamed to 'ACDSee Classic' but it eventually disappeared from the site.
I worked for many years for a small group that had several software engineers. I discussed this with them and they mentioned that the program was almost certainly written in the early days before using 'APIs' became common, and was a great example of efficient programming by people who obviously knew what they where doing.
I've tested it against modern image viewers and surprise surprise!, it's still the fastest. I can throw 1GB panoramas at it and it opens them when other image viewers choke, lock up, or crash. It also still works in Windows 7. It exhibits a few little quirks that I can easily avoid,
but it still works just fine and is used daily. I visit the ACDSee website once a year and it's nice to see that folks are still asking about it and waving it's flag. Of course, management won't admit anything. They want people to buy their be all, do -all (expensive) versions and have an army of paid 'professionals' to trumpet it's merits.
Thankfully it's still widely available on 'those' sites and I'm constantly seeing positive things being said about it in forums.
Wow, I said all that and didn't spit blood or foam at the mouth, maybe I'm learning to relax in my old age.
...but don't call me old.
@jura11 brightly lit scenes with either poser lights or a combo with the envirosphere render pretty decent. The noise problem only gets bad when using indirect light to light up an interior or when light sources are small compared to the area they light.
This depends,interior scene in my case is very easy,if you want to use only one sun or infinite light and yours interior is closed,you can run to issues as will be dark and there what would help is ISO exposure control
I sometimes use as shrvrdavid pointed out,this work for me too and sometimes I use too several lights,i will post renders later on which has been done in SF
Second bit,literally I would jump if SM would add ISO exposure control to camera and if they added mesh lights too
Would be interesting having feedback from other Intel HD Graphics users.
Who knows... may not be a chance we both have this issue on a similar graphic card?
But I guess it's a quite widespread graphic card family, so maybe the issue should be more widespread as well..?
Btw, since I was distressed by not being able seeing materials in preview, I made some testing during last days (before having that dreadful "crash" issue I'm talking about in the other thread.. :(( ) and found that "image_map" textures did show in preview, so I ended up using those when I couldn't do without the preview.
Surely not a solution and quite limiting, but maybe could be useful to know in desperate situations.. :D
(assuming the same applies to you)
Ah, this clears things up, thank you!
So I think I'll be experimenting with normal maps and color maps tonight (crossing fingers - see below).
Interesting addon link also, I'll have a closer look to that as well.
Yesterday my testing has been halted by continuative crashes, seems like I can open no more even a secondary backup file of the same scene that was working fine before this crash on another file..?!
Oddly two saves of the same scene corrupted together???
Basic scene, and other saves of low complexity scenes still open regularly.
As usual, I solved my own problem. I deleted the preferences and let it recreate those files, then copied my libraries prefs back from backup and everything is as it should be, at least with that particular problem. No idea how it could have gotten that odd path into its head.
for a production render (That's Firefly or SUperfly) you will have to set up the materials for all the objects and all the materials in that scene. The setup toon render wacro will only get you so far.
One thing it does that may be wrong is it keeps the image maps attached. Usually you don't want image maps attached. for toon style tenders. It doesn't look cell shaded.
Also the Document display style has nothing to do with a production render. It only affects the PREVIEW render. Some people find the preview render give the results they want without waiting for a production render.
Whatr you probably need to do is make a simple skin color shader like shown. (Note the falloff and line values. Then apply it to his whole body. Then give the car the same treatment. discard all the existing shaders and replace it with a simple toon setup.
Looks like your connection to Graphics Forum was lost, please wait while we try to reconnect.