i uninstalled the latest update for this reason: moving objects in increments using shift/arrow seems to be broken. i use this a lot, like when you drop a terrain & it buries itself wrong, or you work on the terrain some more & it ends up similarily repositioned, so then you have to put it back. the shift arrow thing no longer works & hand-dragging the terrain or ground is a nuisance. what the shift arrow thing does now is just flip thru the object menu. 

i tried cancelling the update. this did not work, it claimed something got corrupted, the version name was still there & the problem as well. ended up reinstalling during the wee hours.

yeah. i just needed a rant. finally got it all cleaned out.

Quote - One of 2 things:

1. CLick the ghost icon in your collections
   2.  In Explorer search for files begining with ~~ & select all & then delete all

I chose #2.

but! they come back :cursing:

i also deleted the store .ds file from the my docs/vue folder. but! they come back. :cursing: so i unchecked the "check for new content" box! but. they come back. apparently unchecking this box is a ruse on the part of vue, it does absolutely nothing. finally i had an inspiration. i changed all folder names & deleted all the folders that had nothing but store items. NOW they stay away. BUT!  now when i load vue i get nagware, for crying out loud. "vue must replace these folders or you will never see the new items!" wah, cornacopia. haven't figured out how to get rid of the nagware message.& i'm still getting the nagware. went to the cornacopia forum, somebody's bright idea was "put the folders back" to get of the nagware. but! if i do this all the deleted items may mysteriously return. in the long run it's quicker to put up with the nagware than delete ~~ items every other week. boy i am i steamed. am i inclined after all this to even remotely consider buying anything from cornacopia? hmmmm....

thanks. i like playing with the hazes, i find if i turn it down too much it looks a little flat or something. 

one thing i noticed with godrays, the graininess seems to be extended somewhat beyond the cloud itself, basically increasing graininess in the sky color. thought this was a bit of a nuisance to get rid of. found lowering the cloud opacity helps here somewhat.  

i've been experimenting with "optimize last render pass" since many other ppl have recommended it. mostly with relatively uncomplicated things. a few of them have come out with smudgier areas, or a little flat. render time was 1-3 hours using a spectral atmosphere, for what was previously 7 (not counting godrays). so i will probably be using full quality most of the time. which means where do i put the quality boosts, these increase the render time. for example, i'm often running 2+ on the sky, fog & haze panel. lowering this unfortunately changes the color/quality of the sky too much for my liking. seems it's easiest to decide first what you want the quality to be, THEN design the atmosphere for best results. some ppl have said you must have 4+ for rendering godrays, that's the only one i've ever tried. most of the time i've aborted the render, since it wasn't practical & kept my computer tied up too long. if they've fixed the memory leak it's now worth a try to render godrays.
 
notice they also fixed the anti-aliasing, where it got stuck on "soft" & water turned to metallic sludge. crisp seems to work now.

i just have the latest patch on, seems they fixed the memory leak & my rendering is a lot faster. as a matter of fact it's about 1/3 of what it was, so far experimenting w/ "optimize last render pass." godrays & water may be saved from oblivion....

hmm, could be interesting for some things. i'll take a look sometime.

what does turning off the transparency do to the look of the water? also, would objects/terrain under the surface no longer be seen?

makes no difference if the sun is attached to camera. to test this: create an atmosphere, place sun, write down sun coordinates. save. without even closing the atmosphere editor, reload the atmosphere you just saved. the sun position will have slipped. saving under a new file name will also make it slip.
 
i believe i'd tested it before with attaching the sun to camera, with no difference. i just did it again a second ago, my original sun coordinates were azimuth 83.47, pitch 131.09. when reloaded the coordinates read 73.06 & 134.01. almost a 10 degree slip there, which like i said will move or even lose a rainbow or godray.

i have emailed eon about this, they said something similar & mentioned something about them making sure the atmosphere was consistent with the preview or something. it is very easy to reproduce this. the way they worded it it seemed pretty plain they weren't going to bother to test this. i have a package up here with atmospheres & had to correct them all, so i'm very familiar with this bug  :o

the worst one is the atmosphere bug which you'll never see if you make the atmosphere in a scene file. if you save it as an atm file, the sun will have slipped. sometimes a little, sometimes by as much as 10 degrees. which is enough to lose a rainbow or godray. my "workaround" was to write down all the numbers & calculate the slip, then get it to slip where i wanted it. a real pain. once it's "fixed" in this way the atm file will be stable--unless you save it again, of course.

i've seen it occasionally, once with the ground. also if you adjust the aerial perspective too much your sky will change...

godrays & water are the kiss of death for render time. i've given up on seascapes & godrays.