I have poser pro 2024 64bit on win 7. Had the same problem. After a while all the icons start to vanish as I scroll the library. I updated AIR and the problem seems to have minimized. That and I deleted the c:/users/user/AppData/Local/IconCache.db file and rebooted. Where user is your user name. I still get an occasional dropped icon but nowhere as bad as before. Plus I use an SSD for my poser drive. In fact I noticed this acted up when I swapped to the SSD. Was still a problem before BUT I was losing ALL the icons as I scrolled when I switched to the SSD.

Quote - > Quote - For example, if I single-click on an item in my Library to select it, then I single-click on a folder to expand the contents of that, I get a pop-up asking if I want to move the item into a folder - not to the folder I clicked on, but to another one several lines lower down!

I think the Poser library drag-click sensitivity issues are a separate, and known, problem which is peculiar to the Poser library.  In that case, it's a known Poser issue which seems far too often to be blamed on the user's mouse settings.  The Poser library is... problematic.  It was strongly hinted that some of use were Luddites, when we suggested that using Flash for the library and linking Poser functionality to IE might not be a good idea.  Sigh.  That Poser library has bigger issues, IMO.  A pity, because I quite like how it looks and what it does, most of the time.  I do hope they repair it one day.

 

The problem I note above, however, seems to be a different issue.  It affects programs other than Poser, but is most intrusive in Poser, due to the default sentivities of the Poser interface.

I have contacted their tech support with the issue and they first claimed it wasn't happening with them until I provided an illustrated repo path. Then they claimed my mouse was not sensitive enough and to go change that in the windows settings.

I also reset my USB devices with no fix.

Basically what happens is if you have expanded a menu item to its larger thumb size, clicking on a lower folder causes that menu item to collapse in size causeing the menu to shift UP under your mouse. The menu think this you MOVED that item cause its now NOT where it was while you still have the mouse down during your click.

Its simply too sensitive.

Move event happens maybe 1% of the time. Sloppy mouse clicks happen like 99% of the time. You should have to click and hold the item to move it and the hold time should be signioficant like a second.

You can avoid this by clicking super fast but not all of us click like this. And I have heard this complaint from others using poser.

This is an old bug. Its happened in older versions as well. Its usually manifested as the hip becomes disconnected from the legs and the legs won't pose or move but the hip can be moved. This is usually caused by a cross talk situation in which some clothes have exactly the same figure number as the figure or some other clothes.

Did the symmetry bug ever get fixed in sr1? For me if I use the symmetry tool and swap right and left legs on v3, it copies the FBMs into the individual dials on each body part creating a mess. Arms seem to work fine. I'm almost forced to write a python script to do symmetry.

There's a problem with the symetry feature. Essentially random dials get set on your figure if you swap left and right. This happened with my clothed figures. All of a sudden body  morph dials or body part dials get random values.

BTW if python gives you an error in poserpros, you can copy the msvcr71.dll file from your poser 6 or 7 setup into the windows/system32 directory or the poserpros directory so poser pros can find it. That fixed my python crashes. for some reason they didn't include the dll with their version.

On a 64bit system with a 64 bit OS I feel Pro runs a hell of a lot better. My renders look fantastic (less texture compression to get it to render) and it runs faster. I can do larger scenes as well. Seems to be a lot less buggy and the interface runs faster. Haven't tried the talk thing but it looks customizable since it runs on xml files.

I use poser professional to create subscription stories and this was worth it to me. I have my own batch render python script so I don't use the queue but its a nice addition for someone with no batch rendering ability. Plus Pro seems to play nicer with shared libraries across multiple machines.

I wouldn't call it poser 8, more like poser 7 sr1.

When I render in poser pros, not using ffrender it still does better and renders larger scenes than poser 7.

Anyone have WinXP64 and run Poser Pro. I have this set up on a 64 bit system. It runs great, no problems. Runs a lot faster AND most of my textures don't compess all to hell to get the scene to render anymore.

One thing I noticed is in the process manager, winxp64 still shows poserpro with the *32 extension on it. So does xp64 think poser pro is a 64 bit app?

I use poser 7 on a dedicated xp64 bit machine (only has 7 on it and used for nothing else). Works even better than a 32 bit OS. I can render stuff I can never render on my 32 bit machines. And having a 64 bit poser that can use a lot more ram will be beneficial especially to all those vicky 4 people. V4 eats up a lot of ram and is one of the reasons I don't use her. The manager option also sounds cool. I currently batch render with a custom python script I wrote but being able to fire off the render then go back to pose the next panel without waiting will be awesome. The $199 is a bit pricey but I think its worth it for people who make money off poser and have a 64 bit system. I have 3 dedicated machines for rendering plus a work machine for regular mail and net. Now if Pro had a distributed render farm option I'd be a happy camper.

Your shadow maps are set too low in resolution. Increase their size or use raytracing and that should solve your problem.

$200 for 129 panels is too cheap. I'd say $50 to $100 per comic page in the poser arena is pretty fair. Thats about what I pay for work.

I also deal with 5 pages at a time when purchasing. That way I can correct stories and the artist gets paid in installments.

Thanks. Yes I already have a tutorial on this method but am seeing if I am wrong that the ALPHA mode simply doesn't work. I thought maybe it might work with gif or png with transparent color but that is a bust as well.

Yeah that's what I do as well but it would be handy to just say the arms, legs etc all should just use the hip material and do this with a simply copy shader.

Quote - > Noticed problem #5 too : "delete" not working. Instead the library window moves up one level, for example from "characters" to "libraries".

No, that's just a focus thing which also happens in P6: If you click delete while the library has the focus, you just go up a level. Allows for keyboard-only navigation in the library.

But the real delete bug exists, I have it too. Apparently it seems to happen after rendering. Deleting from the hierarchy menu still works.

No there is still another bug with delete. If your scene is populated and you hit the delete key to delete a figure or prop there is a huge delay (like up to 10 seconds) in which you can click on another item and that other item then gets deleted instead. Its a huge delay problem. The delete while in library view issue is also annoying but not destructive.

1. Saving poses for Magnets does NOT save scale info even if you check on both transform and morph target options.

2. ERROR MESSAGES SUCK! Sorry efrontier but this is totally unacceptable and has been this way since Poser 4. For 4 versions you STILL won't tell us which textures failed to load, why the renders failed (more specific than that aweful generic out of memory error) or a whole lot of other errors you provide no specific info on. For example, I have had rendering with raytracing just give up and produce a grey picture (background color). No message. To date the system STILL will not tell me WHICH texture did not load when I get a failed texture load. This is a bug and a careless one at that since programming wise this would be very easy to remedy. How about a log file? Maybe for each step of rendering you print out to an optional log file what the renderer is doing so we can review the log and see where it bailed. But the current error messaging is down right horrible and has been this way for 4 versions.