I just tested this in both C5 and C6. The scaling behavior in the Vertex Modeler is identical as far as I can see, unless I'm not understanding you. You have to grab the small tan colored squares that are present on each side of the bounding box to resize (pull) the desired side.

The behavior of Scale in the Assembly room is a different story. In order to get the same results as in C5, you have to go to the Motion tab and under the Transform heading, change the Lock from "Hot Point and Center" to "Hot Point Only". Unfortunately it doesn't default to that setting so it's an inconvenient  PITA.

Why not just wait for the next update and see if things improve? It's supposed to be coming soon.

Thanks for the consolation, Mark. I've actually found a few others, both on Mac and PC, who can confirm this on their systems so there's still hope. It really seems a minority though. We're "special" LOL

Well, I heard back from Craig at DAZ and he can't reproduce the problem so looks like I'm a screwed pooch..... :(

Quote - I am on a PC and before answer your first question I did a test and no problem here too.

Ok, thanks.

Update:

1. I uninstalled C6 V6.03 and removed prefs files from Documents and settings.
2. I reinstalled 6.00 and everything worked fine and as expected.
3. Installed 6.02 update and everything still worked fine.
4. Installed 6.03 and the problem returned.

I'm baffled.
Thanks for trying.

Just FYI:
System Specs:
AMD Athlon 64 3400+
2 Gig Ram
Windows XP Pro w/SP2
Ati Radeon 9550 Video with latest drivers

Quote - Hmmmm, it's not happening here. I just love inconsistent issues. Glad I'm not the programmer that has to figure it out. Go ahead and submit a bug report to DAZ. It's these types of "exceptions" that actually can be symptoms of other issues that can come back to bite later on. Getting it on the board now will pay off later. :)

That's not what I wanted to hear, Mark! LOL
Thanks for taking the time to check that out. I wonder if it's not a PC problem as you're on Mac...
I pity the poor programmers too. So many variables. "it only happens when I sit facing east on tuesdays"

I did report this on the bug tracker btw ( 0021797). Actually, I tagged it on to an existing report that I believe is related. In the meantime I'll just need to remember to remove unused masters so it's no biggie really, but as you say, it could be symptomatic of other issues that could affect everyone later on.

OT: looking forward to your C6 tutes on VTC! Whoohooo!

Thank you both for responding. :)

GKDantas- Yes I have 6.03 installed. Also, nothing is grouped so that's not my problem either. If I drag objects from the browser that were created with versions prior to 6.03, the problem doesn't occur. If I create a new scene using 6.03 and save (drag) just one object from the scene into the browser, it will save ALL objects and shaders in the scene along with it. If I then create a new scene and drag the object I just saved from the browser to the new scene and look in the objects and shaders tabs, all objects and shaders from the previous scene are present. Yes, you can then use "remove unused objects/shaders" but it seems you have to do it twice. It's a puzzle LOL.

I did check the DAZ bug tracker and one guy reported a situation that I believe may be similar. He said that the file sizes of objects saved to the browser in 6.03 are much larger than in previous versions so this could be because everything in the scene is being saved along with the object.

Thanks again fellas

John

Conniekat8 - Glad they helped. I know I enjoyed them :)

FranOnTheEdge - Sounds like a codec problem but glad you got it figured out. Frustratin', ain't it?

I've gone through 3 hard drives this past 1 1/2 year. I'm in no mood to even talk about it haha. JohnOverTheEdge!!

Just a suggestion and no pressure for sure, but if you get a moment, you's (that really should be a word!) might want to drop a small "thank you" message to E-Z as he put a lot of time into those tuts. Hopefully he'll do some more :)

John
**
**

Quote - Are there any simple Hexagon tuts?  I've just tried to follow those MysticNights tuts, and it's impossible - they assume prior knowledge.

Fran-

You should check these new tuts out if you haven't already. They were done by E-Z and are fairly easy to follow.

John

forum.daz3d.com/viewtopic.php

Wow! I'd be happy to be half that good. Do you do this for a living? I'm a hobbyist but still having a blast anyway. Fantastic work, and have to say, I enjoy and look forward to your posts. :)

John

A useless tip?

drats, foiled again....if I had only read on past page one I coulda been a contender.

I got an answer on the DAZ forum  that this is a bug and has been reported. Let's keep our fingers crossed and hope it gets fixed in the next release.

I shot myself in the foot by deleting those files because now I have several headings in the browser named "basic" instead of Basic Clouds, Basic Plants etc.  LOL. Fortunately the files can be restored.

Update: this is suspected as a bug and has being reported (not by me). Apparently it only affects PC since you haven't experienced the problem and are on Mac right?

Thanks for responding, Mark. I conducted a little experiment (I never learn!) and what I did was search for all "infos.txt" files and delete them. Apparently these are generated when you choose "create index files" from the browser. With these files gone, everything sorts on-the-fly as it should now. It seems once I create an index file, all entries are frozen in their current order and no further sorting is possible. All subsequent additions to the browser category will be added to the end of all other entries regardless of it's sorting position. Weird. The only reference to the list on the left hand side of the browser (Sky, Landscapes etc.) is in Carrara.Priv so maybe there's an answer there for that. Maybe some cut and paste will fix things. 

John