There are a lot more problems in P6 than just the memory bug. The dial response problem referenced above, some remaining focus issues, the memory structure design error found by a partner at release time, features in the manual not enabled in the code, etc., etc. So if they are taking the time to try to address everything in one go, more power to them. Historically P4 took a couple of SR's, PP 3, P5 4 of (really 9 as there were 5 attempts at SR2 ;-) so it would be good if CL demonstrated that they could substantially fix a release in one pass. But the effort at the Content Update suggests otherwise of course. (By the time my P6-in-a-box arrived the CU was available, so I hate to imagine how bad it looked before the CU, 'cos it's still pretty bad.) And P6 still has all the bugs and slowness of P5, plus all the bugs and slow downs of PP and the bugs of P4 and ... As to 1 month being too long for the memory bug fix, that might be true if and only if the bug was a P6 development bug. There's a real possibility IMHO that it's no more than finally "hitting the wall" with the memory management bug that has affected all Poser versions with increasing seriousness. (Adding more resident code to an app which is already saddled with an out-dated memory structure.) Fixing that would be very tricky, especially - as indicated above - because CL has clearly little practice in fixing bugs in prior release :-O And did anyone else note a reference in that post about the memory structure design error by a development partner to CL, which said that CL should be able to fix easily because it is in "live code"? Which implies parts of Poser are "dead" code? Each development shop has its own coloquisms, but that sounds awfully like they do not have access to every piece of source code...

The P5 dial remove trick still works as you can see in my screen capture, but as it doesn't affect the width of the parameter dial window, it should still all fit without it. I don't use the expand out triangles on the parameter dial window very often, but I can still just access them if I do need them.

Don't you like how the "UI Dots" header stays when you hide the dots? Also the click-anywhere-to-close-the-library-palette "feature", added by Larry W in P5B2.1b when I complained that Library palette handle goes BEHIND other windows, has been dropped in P6 - even that handle is still separate from the library palette. EDIT: Ahh, I see you run 1280x960 - square pixels - I only read the 1280! I run 1280x1024 as 1280x960 is not supported on my video edit package, and I hate resizing my desktop between apps.

Message edited on: 04/22/2005 11:27

Under P4 & PP on the tool's HEADER BAR to re-orient. On P5 & P6 on the TOOL itself anywhere EXCEPT the Tool's Header Bar. Another case of developers who don't use/know the product they are "fixing"?

Hi all. I'm glad that my P5 UI tweaks got such wide acceptance - even if I never used P5 much myself (I was one of those for whom P5 was literally unusable until SR4.1.) The place where most of the communication on this topic has been carried on is PoserPros > P5 Tips & Tweaks. Netherworks confirmed early on that the dial tweak still works (thank goodness!), but that the libraries tweak should NOT be tried on P6. I have P6 SE-in-a-Box, but have been so busy with my real life so far this year that I've not even installed it. Hopefully I'll have time soon to further annoy CL by improving their interface, and take Nether up on his offer ;-)

vim (Vi IMproved) from www.vim.org also has a poser syntax file from _dodger

mathman, Netherworks,

Re #20 this bug existed in P5, I reported it on the very first P5 release, but it was never addressed AFAIK.

Re crosstalk, also look at Hogsoft's free Crosstalker, which will do the 2 seemingly contradictory functions of enabling crosstalk in P5 when you need it, and disabling it in P4/PP when you don't want it! Yep, the 2 bugs (well technically one must be a feature, and the other a bug - but there's no consensus amoung pees as to which is which ;-) are so similar that the same technique can be use for both.

I'm in the HuryyUpAndWait Club, but my suspicion is that Command Bar support from new windows has not been ENABLED. I.e. Something overlooked rather than disabled per se. As each is a separate window, and thus a separate task to Windows, (unlike on Mac), then CL needs to enable those Command Bar options to EVERY window, so regardless of which window you are in the current window can react - and then pass the info back to the main window, eg. Shouldn't be too hard for CL to address if they have the motivation. This was a problem in P5 too with P4PyE, so I'd hoped that it would be fixed in P6. It was a concern as soon as I heard P6 made more use of separate windows.

Go to PoserPros and look in the P5 Tricks & Tips forum. The instructions are near the top in a post from Netherworks. Joe has alos tested that it still works with P6. I believe it does remove the links to Internet Explorer browser routines. When tested on P5 (pre SR4/4.1) it reduced memory footprint, all accesses to the 'Net, and most specifically speeded up intra-process communication significantly (i.e. when switching between P5 main window and the Parameter Dial window). The removal process is not difficult, just a little exacting, but as long as you don't overwrite the original file, you can make multiple attempts to remove it, if you fail to get it exactly right the first time.

Let's hope the issues raised by JHoagland are fixed! Reason is that many/most of these are directly related to the design choice (?) of a separate Windows' window for the Parameter Dials (not a bad choice on a Mac, but a disaster on Windows as it has all the overhead of switching to a 2nd application). So what? Well P6 appears to be using a separate window for the scene window(s) in addition to the Parameter Dial! BTW, removing Content Parasite reduces the impact of the problems referenced by JHoagland - presumably because the intertask communication between Poser 5 and Internet Explorer routines "butts in" during every intratask switch between Poser 5 and its Parameter Dial window. No fix for the focus issue though (which should never have cleared the Beta stage of Poser 5).

Also try Howard's own support site www.hogsoft.com

Attached Link: http://www.hogsoft.com

Great, that was exactly how I expected that feature to be used when I pushed for it. I'm pleased some have seen the advantages of exploiting it.

I'm very glad to hear that someone likes that Notes feature! ;-)

If you've not already, check www.hogsoft.com for info, and an explanation as to the cause of the need for CR/CRPro - basically it's an unfortunate interaction between NT/2K/XP software protection and a bug in Poser (written for Win9x), and affects other applications as well as Poser - e.g. some Win 2K's own network file transfer routines ;-).