Quote -  

OK Guys, bonus points if you can name the characters in this render.

Its called, "At The Malt Shop".

You see it full scale here;

http://www.renderosity.com/mod/gallery/index.php?image_id=2414494

 

most excellent idea and render! `¬)

Quote - Is the board at RDNA going to be hoarded by poser users? Just saying this due to the fact that the concerns / tips will be quite different from us DS users and I can see it becomimg confusing...

Just had a look and there are two top levels under 'Reality 3 official forums' , one for reality for poser (which is the original one there) and one reality for daz, so they seem to be seperate at the moment! `¬)

Quote - That would be awesome mbin,  I know when I want to find specific information about how to do something if it's posted on Paolo's forum we will always be able to find it. It's just a shame that Daz removed the Reality thread and all that wonderful information is now gone.

...I hasten to add these are things from the old daz site forums and not the recent forum on their new updated site.

Has the 'archieved' forums also become un-accessable? (I can't remember what the change to the address was to get to them... although the images not showing up was a pain anyway!)

Thanks for the info Poalo, I'll see if I can sort out some things from my saved info that will be worth posting on the runtime dna link when you post it! `¬)

Callad; it was just a thought... `¬) and yes, I really must get my dinner on, and yes the washing machine has been blinking for the last hour or so, trying to tell me its finished its load! ...looking forward to some new things! ...I might even see if I've got time to do a render of my own... seems to have been awhile! ...oh well!

Glad it is solved! `¬)

EDIT; Ha! Paolo beat me to it! ...I probably rambled on a bit! `¬)

The default rendered image you end up with is .PNG. This is not related to any images used in the original scene for either maps or backdrops. I assume for back drops you mean setting an image onto a plane within your daz scene before you render... http://fav.me/d4aky2i You can either add the image to the plane in daz studio, or you can load the image onto the item in the Reality interface as indicated here...

I hope it is not too confusing in that I am illustrating with an older version of DazStudio and Reality?

...as far as render size goes, I generally render the same size resolution of my pc screen which is in my case 1920 x 1200 pixels. That means it will fill my whole screen when viewd full size. I cannot see much reson to render bigger than this, as otherwise to view full size on screen means having to scroll around the window!

On the other hand, if you wanted to print out your render poster sized, you might want to render an image with higher resolution but this will depend on the printer resolution. This is where your 'ppi' comes in. It gets a bit complecated, as it can take several 'dots' on a printed image to resolve a single pixel colour...

ppi is a bit redundant when it comes to a monitor, as most 'standard' monitors these days (rather than top rate graphics monitor which would/could have far higher resolution), are 1920 x 1080 for widescreen (my screen is 16:10 rather than 16:9 - the ratio of the width to the height). Depending on the physical size of your monitor will determine how many pixels per inch you will have. A 1920 x 1080 pixels on a 28" monitor will be far less ppi than on a 18" monitor...

This is just my opinion, I'm sure others may be able to give good reasons to render at other sizes...

Incidently, I would not render full size you want until you are happy with all your settings. I generally start test renders at about 50% size, as I can see the results faster. Once most of the tweaks are done, I may go to 75%, and when I am happy with the whole scen, I will then go to a full 100% size render. That way, you can see how your scene / image progresses as you add or change items. Until you are very familiar, it is probably not a good idea to fill your scene and set it all up before doing a test render. I will start a scene and test render each item I add or change. Sometimes I will set up a completly seperate scen from my original if I want to test some settings on only one object. Once it looks right, I can then add it to my main scene knowing the settings are right - rather than rendering lots of other things in the scene that I'm not interested in at that point.

At the end of the day, if your target 'audiance' are viewing on a monitor, then its probably best to match the 'avarage' monitor size, and if your target is to print out posters, then you will likely need to render larger to take into account the requirements of the poster size and the capabilities of the printing process used. Some usefull info here if you really want to delve into it... (personally it just made my head hurt! `¬)

 http://en.wikipedia.org/wiki/Dots_per_inch http://en.wikipedia.org/wiki/Pixel_density

Quote - Ok i will try it during the week end

I usually use a mix of DAZStudio objets and Poser ones

And for the snoot problem with softbox .when i try the gadget for move (like the arrow ) the gadget move but not the snoot and i cannot see the parameters slider like you show in the you tube video  ,the one Mbin suggest  earlier in this thread

In ds3 (I assume it is the same in ds4), in the 'scene' tab where the scene items are listed, you need to make the snoot visible. Then to extend the snoot, drag on the z-scale box rather than move it with the arrow. The very first time I tried it, I ended up moving it rather than extending it too! `¬)

Finally caught up again... seeing Callad's 'projector' reminded me of some examples of using transparancy maps with mesh lights that I posted over on D.A. Although they were originally meant to illustrate how to simulate beams of light using the fog prop, and an alpha map of the leaves and branches of a tree, I thought I might post it here, as I'm guessing that once Callad has released her projectors, they may be possible to use them in a similar way?

 @Callad if this is the case, maybe you could add some appropriate alpha maps to the set you produce? ...or is it possible to add some colour versions as texture maps, for a 'stained glass window' type effect? ( http://fav.me/d4xnsra ) It would be really great if what you are doing could also be used like this?

The links will provide some further text and also additional links. The alpha map linked to was originally made by Kenneth Rowe, and there was some examples on the old Reality thread on the old Daz site forums... (this is in daz3A, but the principles should be the same!) (Link to additional info http://fav.me/d4jvkiw includes links to the alpha map etc)

Method of applying an alpha map to the plane and parent to a spotlight... (link to original post http://fav.me/d595fu3 )

I will try and get some of the info from the old forum thread and post them on http://preta3d.com/forum/ as requested by Amethst25, but may take a while for me to sort out what is worth posting there! `¬)

I can't comment on what ds4 does, (or ds3 either), as I do not use the daz render page (and have no idea of the slow turtle symbol... lol!)

As far as I know, Luxrender simply renders an image which is so many pixels by so many pixels... I gues that if you wanted a final print at 96dpi, (dots per inch) you would need to render the appropriate size image, such that you print a 96 pixel by 96 pixel the size of one inch square? I'm not particularly familiar on how a print would be done from a generated image, but if you want to print at 96dpi to a size of 16x24", that could corrospond to 1536 pixels by 2304 pixels... but I am assuming 1 pixel would relate to one dot... I think this has been discussed somewhere before... If I find a link I will post it.

I also cannot say how much memory you would want for your items, as it depends on geometry, sub division settings, as well as textures etc. I suggest you try rendering the image at small size and then you can calculate how much memory it would take... sorry I can't be more specific! ...have you looked at memory usage in task manager for the Lux process when you hit 'render' from reality?

That all depends on what you have in your scene... as well as how much subdivision might be used. If you want to get a feel for it, open task manager before you call Reality, then watch the memory use in the processes tab of the Luxrender.exe as it parses out the scene file; you will see the memory usage go up, and eventually the lux render window will appear. Check your scene set to a small size and see... I ended up fitting 32gb ram, but most of the time its because I might be running several smaller test renders at the same time. If you look at the memory usage in this way you should get a good feal for what happens to memory usage if you add complexity / subdivision / image size. The one thin you don't want to do is have a scene that takes more memory than you have, as if it starts to use a disk swap file, the render speed will slow down by massive amounts...

Basically the more memory you have, the bigger and more complex scenes you can render. There are ways of conserving memory usage, I'm sure Paolo or someone can give a more expert view on this! `¬)

P.S. as far as physical size goes, it depends on what resolution (pixels per inch or dots per inch you want? - screen size or print size)

Is this a new issue with the latest version, or are you new to reality / luxrender?

You will need to post the render and some idea of settings, but I also suggest you post the question in the Reality thread here... http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2849428&page=1

If you are new to Reality/Luxrender;-

In general, (without seeing the render or knowing any settings), noisy images that take a long time to clear up are due to poor lighting, something preventing the light source from getting to the scene (I think light domes were mentioned at one point?), and is similar to trying to take a photo of a scene at night without a flash or someother lighting... the result is dim and grainy as the aperture of the camera is wide open.

The opposite can be true, where you get a lot of light 'amplification' due to material surfaces glossyness etc... which will result eventually in large 'blotches' that will end up 'whiting out' an image.

I suggest posting to the Reality thread above, and you will soon have several people trying to help; but you will need to give further information. A screen grab of the luxrender window would be good to start with, and then we can start to understand what you are having a problem with!

Incidently, to do a test, simple add an object to a scene and add either a reality softbox or mesh light to the scene, (ensuring the light is in the right direction) and render...

http://www.youtube.com/watch?v=lVch_4d8C3w

http://www.youtube.com/watch?v=v0R8lGZVQmE

although these are for an earlier version, they concepts still apply... `¬)

...at work at the moment, I will try and check back this evening... (If not already answered!)

 Would you be willing to post that in Paolo's forum in the thread called Recipes?

If I get home early enough tonight, I will... otherwise it will be the weekend. I might also look at the w/e as to any other info I saved from the old daz forums to see if it is worth posting there too... although it is only info upto the point when daz redid their site, as I didn't frequent the daz reality forum once we were running here... `¬)

Was the pearl settings for the particular choker in acsel, and did it get updated for the newer reality acsel does anyone know?

P.S. thanks for those that responded to poser/daz preferances! `¬)

Quote - Attached Link: http://www.renderosity.com/mod/gallery/index.php?image_id=2411925

Well... Here's the render I was struggling with, finally finished.

Its called, "I told you not to peak when I was buffing myself!"

 ...lol... very cute cam bot! how did you get it to be so innocent looking!?! `¬)

Quote - Hi Mario.

Thank you for your recognition about the Poser Add-on framework, it's very much appreciated. SM deserves, of course, the praise because they developed it trusting a perfect stranger, Yours Truly :)

... but it's a good thing that you kept up with Poser because...  

... I did have a trial version of Poser once, probably poser 3 or something many many years ago. I can see that Daz3d is not aiming at application development, and being as Poser now can support Genesis, the content provided by daz is now fully Poser compatible... The only problem is that for those of us who have not kept up to date with the Poser upgrades, it is quite a steep sidways move to now jump on to PoserPro2012... Certainly something that is becoming more attractive though, especially with what's going on with Daz? I wonder if Smith Micro are likely to offer a 'package deal'... buy Reality 3 for Poser, and get Poser 9 (insert crazy offer price here) and upgrade to Pro 2012 for only... `¬) ... now that would be interesting! For those that have used daz studio and Poser, which of them is prefered and when they both have Reality support, which one are you likely to end up using? (or would they both have different advantages/disadvantages?)

Quote - > Quote - Crystan, you'll find diamond in the Gemstone material drop-down list, which will set the IOR for you. Personally I do not set it to Hyper Realistic.

There was a setting for Pearls but it was on the old Daz site, so cannot find it for you. There is a IOR setting for pearl in the same drop-down list though.

Sharkbyte, funny how we both rendered redheads with the simular poses.

The problem is that the IOR alone isn't really giving the effect I was after. It just looks like glass but the background beyond looks a bit more bulbous than usual. I was really looking for some thin film settings which aren't added by the drop-down so I can get that same irridescence normally associated with shiny gemstones. Well, the render didn't come out too badly in the end regardless. I just have a bit of extra postworking to do.

Maybe a bit late now... but this is a post I saved under Reality/Tutorials on my hard drive. Not sure if its the one being refered to, but maybe it helps? `¬)