I've installed the update several times and all seems okay so far, aside from a Create Magnet problem. The magnet gets created on the body part and it works, except the Mag Zone is no longer centered around the Mag Base. It's always below the Base, no matter what the body part. Moving the Zone up doesn't help, because the affected body part area just moves up with it. It's out of sync. It used to be fine before I made these updates (and I always kept up with the Smith Micro updates). I also have Daz Studio installed with DSON, in case that's a factor with this problem.

Is there some configuration to the files I can do to fix this? I've put a ticket in at posersoftware and that was submitted, but when I try to view the ticket I'm told I'm an invalid user. I have no idea what username/email and password they're looking for, so I'm not sure what to expect from that help desk. I'm hoping someone here has come across this problem and knows the fix. Thanks.

I was faffing about with magnets a couple of days ago and didn't have this problem. Are you running the stable version of 11.2, or one of the betas?

I didn't run the betas, so I guess the stable version. My most recent install was yesterday. Everything. When I first opened up Poser, the magnet DID work. Then I added my other libraries (an old Poser 5 and my DAZ library) and the mag zone problem appeared. I've removed those libraries and tried again, but the problem persists. I've used obj files in my Geometries/deform folder instead of the obz files. I've added/removed subdnull.obj to my DAZ DSON folders. No luck. Sometimes, I get these teeny weeny magnets, probably thanks to all my futzing with the files. That's why I reinstalled again yesterday.

I'm going to try moving my Poser content under the directory where my poser.exe file is next. Maybe that'll make a difference. I got an email from the Help Desk (they got my ticket!), so they may have an answer.

Thanks!

SamTherapy posted at 12:49PM Wed, 09 October 2019 - #4366516

I was faffing about with magnets a couple of days ago and didn't have this problem. Are you running the stable version of 11.2, or one of the betas?

Hi VedaDalsette.

When I do this, the mag base and magnet appear on the arm just like you get. The mag zone is centered on the arm which is normal, not on the mag base nor under the arm like you're experiencing. I tried this using Dusk and Michael 4 and the magnets are created like I described. Just tested in Poser Pro 2014 and I get the same results as I did in Poser Pro 11. No idea why you're getting different results. I hope you get a fix for this soon. If you do, please share what's going on in case others experience this issue.

Lee

You're right. The mag zone s/b centered on the body part, not the base. But mine's always UNDER. How does Poser know I'm an underdog? Anyway, I'll definitely share the fix if I get one.

LeeMoon posted at 1:33PM Wed, 09 October 2019 - #4366519

Hi VedaDalsette.

When I do this, the mag base and magnet appear on the arm just like you get. The mag zone is centered on the arm which is normal, not on the mag base nor under the arm like you're experiencing. I tried this using Dusk and Michael 4 and the magnets are created like I described. Just tested in Poser Pro 2014 and I get the same results as I did in Poser Pro 11. No idea why you're getting different results. I hope you get a fix for this soon. If you do, please share what's going on in case others experience this issue.

Lee

When you report an issue like this, please, please, please give us vital information so others can try to reproduce your problem:

Go to Help>About Poser and capture and post a screenshot of your version number

Let us know what operating system you are using.

Without this vital information, we can't hope to figure out how to help you.

Thanks. PoserPro version 11.2.296 and Windows 10. I did screenshots of this info and my systems/graphic info. I have the latest Nvidia Studio driver. Appreciate the help.

Glitterati3D posted at 3:21PM Wed, 09 October 2019 - #4366523

When you report an issue like this, please, please, please give us vital information so others can try to reproduce your problem:

Go to Help>About Poser and capture and post a screenshot of your version number

Let us know what operating system you are using.

Without this vital information, we can't hope to figure out how to help you.

At the first had I thought yo might have an issue with the setting of compute magnets in world space but having a closer look at your screenshot there is definitively something wrong with your magnet !

this is how the mag zones actually should look like in P11

You said you removed the libraries. Did you try restarting Poser from a Factory state in General Preferences?

My mag zones never looked like that, and I've been playing with Poser for years. In my content's Runtime/Geometries/Deform folder, I keep alternating between my zipped obj files and unzipped files, but it seems to make no difference.

gate posted at 4:33PM Wed, 09 October 2019 - #4366532

At the first had I thought yo might have an issue with the setting of compute magnets in world space but having a closer look at your screenshot there is definitively something wrong with your magnet !

this is how the mag zones actually should look like in P11

Also, gate, this is how the magnet looks in the poser reference manual.

Yes, thanks, I tried that several times. No change. And I've been launching it to a Factory State since my last install. Doesn't seem to make a difference unfortunately.

EClark1894 posted at 4:44PM Wed, 09 October 2019 - #4366533

You said you removed the libraries. Did you try restarting Poser from a Factory state in General Preferences?

VedaDalsette posted at 12:34AM Thu, 10 October 2019 - #4366534

My mag zones never looked like that, and I've been playing with Poser for years. In my content's Runtime/Geometries/Deform folder, I keep alternating between my zipped obj files and unzipped files, but it seems to make no difference.

The screenshot shows two copies of each deformer (e.g. base.obj and base.obz), from different installations (see time stamps of files).

Delete the .obj ones (Poser 11.2 only installs .obz files in that folder). Do the same in the primitives folder, especially for the ball.obj which is used by Poser for the Mag Zone. See if the problem is still there when Poser is only using the files from the 11.2 installer.

Obviously, make backups of the obj files before you delete them :)

Snarlygribbly, I've tried using just the obj or just the obz or both. However, I didn't touch the primitive folder obj. I'll give this a try. Right now, however, I'm in the process of copying over my poser content (that'll take a while to finish). Thanks!

Snarlygribbly, had only obz files in deform and only an obz file for ball in primitives (I didn't find a ball.obj in that folder). Same result---mag zone too low.

A year or so ago, I had a problem with magnets. They were really teeny tiny. They went from horseshoe shaped to an arrow thingy. The mag base went from a bar to a disc. And the mag zone was displaced just like now. I found some fix in some forum (Renderosity? DAZ? Can't remember.) but I don't remember what I did. I thought I saved the fix, but maybe I lost it during the update installs. Anyway, I can't find it online anymore, and I can't remember what the fix was. Deleting a file? Editing a file? Somehow tied to DSON? Can't remember for the life of me. And it may not be the fix for this problem anyway.

I may have to adjust to a magnetless life until Poser 12 comes out. (Heaven forbid!)

Thanks.

VedaDalsette,

One of DAZ Studio's content packages overwrites Poser's magnets obj files. I had the same problem that matches your description. I was able to restore Poser original files by copying from another version of Poser that was already installed.

The zone prop is the ball at Runtime:Geometries:props:ball.obj. See if something has messed with that.

By default, Poser installs obz files (They are compress obj files). If there is an obj and obz file, I do not know what one Poser will use.

I have seen issues with Poser loading the wrong objects for deformer props after using DSON. I don't believe that the DAZ installation is replacing anything in Poser Runtimes, it's just that the temporary DSON conversion runtime gets promoted in front of all the Poser runtimes in the search path, so it finds those prop object files first, and one ends up with what looks like the deformers from DAZ Studio. The magnets did still appear to work, but the positioning of the zone was out of sync with its volume of effect. I expect that the DAZ sphere object is not centred on the origin as the Poser Zone sphere is, or some issue like that.

Willdial and An0malaus, thank you. I thought it might be connected to dson but wasn't sure. I'm still getting this result. This is after I'd removed the DAZ library in Poser yet again and opened Poser in a factory state.

These are the files being used.

I've been trying variations of obj or obz but I'll try to be more deliberate. I'm tired of reinstalling Poser. Yesterday, I reinstalled dson, but I saw no change. Right now, though, a dental appointment beckons me (always an ache somewhere). Thanks, everyone! I'll have an answer for this thing yet.

A FIX, THEN FAILURE.

I scavenged more files from P11 off my old computer and took screenshots to make sure I put them in the right folders. I made my newer computer folders as follows.

More in next post.

this sure is strange ... you are right if the magnet is not applied to a body-part then it will show just like in the manual but the moment it is applied to a body-part like in the screenshot it will get a different aspect I tried it on several types of models and get the same result .. they also work like a charm so it seems that your magnet does not automatically apply to the selected body-part !

A FIX, THEN FAILURE continued.

At this point in Poser, I hadn't added my DAZ library yet. The magnet looked good on my Poser library LaFemme.

The magnet looked good on my Poser library Michael4.

I added the DAZ library. Another Poser library Michael4. Another magnet. Looked good.

I added DSON figures from my DAZ library and then gave Michael4 another magnet. FAILURE! And it's that teeny tiny magnet I've seen before.

More work to do.

Gate, in the past I've had the magnet attach to the correct body part and display just a circle for the mag zone. I'm on Windows. Are you on Mac? Does that make a difference? Anyway, I know my problem is something to do with DSON/my DAZ library. Maybe I can't use a magnet when a DSON figure is in the scene. Need to test some more. Thanks!

VedaDalsette posted at 8:39PM Thu, 10 October 2019 - #4366630

Gate, in the past I've had the magnet attach to the correct body part and display just a circle for the mag zone. I'm on Windows. Are you on Mac? Does that make a difference? Anyway, I know my problem is something to do with DSON/my DAZ library. Maybe I can't use a magnet when a DSON figure is in the scene. Need to test some more. Thanks!

LOL .. I'm also on Windows , but it can be that my magnets changed due some adaptions I made for figure creations as I also use these allot ! well it seems that each system can offer different different styles. well I hope that you will find the right solution for your Problem

Okay, here it is.

I reopened Poser. My DAZ library was included. I added a magnet to LaFemme's shoulder. It was fine.

I then loaded the DAZ BizMan figure into the scene. Just moved him aside.

Back to LaFemme. Her shoulder magnet is fine. I then added a magnet to her thigh. It's that teeny one with a too low mag zone I displayed in a previous post in this thread.

Then I added a magnet to BizMan's thigh. Also teeny and zone too low.

New scene, same Poser session. I added a magnet to LaFemme's shoulder. Looks fine. New Poser session (launch in factory state) with DAZ library still loaded. Again, I added a magnet to LaFemme. Looks fine. I'll have to try launching in preferred state later.

Conclusion: DSON messes with Poser magnets. Once I repaired the files (as noted in posts above in this thread), I find I can't use magnets in a scene with DSON items loaded. I wonder if other Poser users can.

Thanks everyone for your help. If you can add to this, I'll be checking!

This is Genesis 2. Imported from a previous PZ3. Have you got any PZ3's saved with Genesis 2 figures in it. The DSON still activates so it is a proper test.

Poser Pro 11.272. Windows 10. (I see no reason to update until I am certain all bugs have been removed or remedied.)

gate posted at 1:07PM Thu, 10 October 2019 - #4366532

At the first had I thought yo might have an issue with the setting of compute magnets in world space but having a closer look at your screenshot there is definitively something wrong with your magnet !

this is how the mag zones actually should look like in P11

GATE! How did you get the extra spheres to appear in your magnet? Mine always looks like the manual.

quietrob posted at 10:37PM Thu, 10 October 2019 - #4366641

gate posted at 1:07PM Thu, 10 October 2019 - #4366532

At the first had I thought yo might have an issue with the setting of compute magnets in world space but having a closer look at your screenshot there is definitively something wrong with your magnet !

this is how the mag zones actually should look like in P11

GATE! How did you get the extra spheres to appear in your magnet? Mine always looks like the manual.

hmmm .... these appear automatically with the Axe when I load em on a body-part I Had em that way as long as I can remember

Quietrob, I know I don't have any saved pz3s with Genesis 2. Clearly, my configuration is off from yours. If you're feeling ambitious, can you compare my files (see above at VedaDalsette posted at 1:25PM Thu, 10 October 2019 @4366626) with yours? Maybe I need to add/remove something. Thanks.

I cannot confirm that DSON messes with Poser magnets. I was able to create a magnet just fine on Genesis 2 Female with DSON.

Maybe it was something with your setup.

FWIW, and assuming it's not broken, Poser does include both a compress and uncompress utility in the Python Scripts Menu, and you can use the UnCompress utility to uncompress the .obz files.

How did you update Poser 11 Pro to 11.2?

Does the Rosity install file cover GameDev, generic Poser 11, AND Poser 11 Pro?

bc it looks like it's just asking to install a new version of Poser 11 (called poser 11.2) which confuses me bc Poser 11 and Poser 11 Pro are EXTREMELY different.

Willdial, thanks for that. Yeah, it's probably my setup.

EClark1894, I've used the decompress script, but I'm not sure what advantage that has for my problem. All I see in the obj files are vertex numbers.

Darkworld, you may have a point. I used the only update provided on posersoftware.com. I thought it said I had to update my PoserPro if I wanted to keep using it. And it did "highly recommend" I uninstall it first. I have a ticket open, but I don't know the status, since I only get emails from the help desk and can't look up the ticket. I can submit a ticket but when I try to view it, it tells me I'm an invalid user. And there's no place to sign up on posersoftware.com. My Renderosity email and password don't work. I'm afraid to reinstall my original PoserPro for fear it won't validate now. Also, I don't think I kept all the Smith Micro updates, and even if I did, they may not work. The app says I have PoserPro, but who knows?

I can’t speak to PPro 2014, but updating from 11 Pro to 11.2 worked just fine and solved my activation issues.

Darkworld, mine seems fine, too, except for the magnet issue with dson figures.

DSON, being essentially a cut down version of Studio, without the UI, will prioritise the DAZ libraries for anything applied to figures it imports into Poser. Since DSON is an add-on to Poser, it gets first go at initialisation, before the rest of Poser has completed loading, so it's entirely likely that any reference to DSON imported figures will suddenly exhibit a tendency to find similarly named deformer prop objects within the earlier search path entires, hence it finds the DAZ version of deformer props, rather than the Poser versions. However, if your poser figures have explicit, absolute paths in them, they will always locate the exact object specified. If the object path is Runtime relative, whichever Runtime is earliest in the path and contains the named geometry object being looked for will be used.

If you never use DSON in a new scene, you will never see DAZ style deformer props. The moment you do use DSON, the possibility exists that Poser will start using them instead. Especially if a scene is then saved and reloaded, preserving the references to the DAZ Content runtime which houses the non-Poser style deformer props.

If you want to prevent this, and are using Poser alone (with DS simply as a library source for figures/props you'll import), you can try renaming the objects within the DAZ Content tree that have the same name as the Poser deformer props. Just make a minor name change, so you can put them back, if you need to use DS again, then Poser will never find the DAZ deformers and will keep searching until it gets the right ones.

An0malaus, thank you for that explanation. I had tried renaming DAZ objs before, but I kept a subfolder in the DAZ runtime deform folder with other obj versions, and DAZ probably found those objs. Also, I don't think I had changed the DAZ runtime props ball.obj name. So I removed the subfolder and made the necessary filename changes.

Anyway, it all works now! Thank you. I changed these DAZ filenames.

I added a magnet to La Femme (you can't see it here because the focus is on the other figure but that magnet is just fine). Then I added a DAZ DSON figure to the scene and put a magnet on her. It's also fine!

Thank you, and thanks to everyone who weighed in on this. I love my magnets!