Flint_Hawk
Extraordinary
Thank you Miss B!
I need to get out and read threads more often, I'm guilty for just looking at the images and skipping over all the words.
poser daz - daz poser,
content creator here, and sadly what sucks from this end is I just like making stuff, I dont like making renders or collecting content, I just like to make content, I like the sculpting and uv process most, and it is hard to have to split things up and do it in different formats, I'm about to drop a bunch of cash in on poser just so I can support the program.
It's too bad all the programs didn't just decide on and share the same file format, so a content creator could just make something in one version like a .fbx .duf . cr2 .whatever - and everyone could then just load it up and use in Maya, DS, Poser, Blender, sidefx houdini, Carrara. etc.
Still to new to all this, not sure what happen to all the 3d apps back in the day causing so many different file types, but I wish they would not have done it. I don't even know what the first type was and I'm sure many many more will follow.
Just it makes it difficult for those of us that just want to make things. I could care less what render engine or program people prefer, I don't understand why anyone cares, most of the time I can't even tell if a render was done in DS or Poser or something else or what engine they used - by looking at it, usually hard to tell. I've got a feeling a lot of content creators have this same feeling I am about to share, when I see someone use something I made in a render, and that person is happy with that render, this makes me happy.
I hope what I wrote is okay? Feeling somewhat reluctant to hit the (Post Reply) button. I'm not to up on my forum etiquette.
I don't think SM have helped either with Poser 11 as I understand that figures loaded into Poser and then saved will no longer work in earlier versions without modifying some aspects, that just gives vendors further headaches.
That has always been true with new versions of Poser, Hornet. And it's not a 'further headache' - it's just the way it is.
And, on top of it, the item will load after a short warning message. It is a very simple change of one line in a Poser file to change it to work in other versions.
But, if you create something in Poser 10 and someone tries to load it in Poser 7, they will get the error message as well if you didn't take the time to change the version number.
I was aware of this, I was going to say issue but that gives it more importance than it deserves, as you say it is easily sorted. I had another issue in mind and I should been clearer. I have lifted a comment from a thread elsewhere to explain.
"The changes introduced to P11 to support subdividing morphs affect every cr2 or pz3 passed through the software, whether that user activates subdividing morphs or not. We weren't warned about this, but it affects everyone and everything."
If this is the case, I say if because I do not have Poser 11 so I cannot personally verify it, then it is an issue for me. For example, if I have Poser 11 and it is working nicely and for some reason the deactivation process kicks in I cannot revert to Poser 2014 to continue working on my scenes. On the other hand, if the same happened to me using Game Dev, I could revert.
I will hold my hand up and say I don't like the deactivation procedure so this may be just a personal issue but, if correct, I can see some difficulties for vendors.
I do not expect to be able to use features made for later versions of Poser to work in earlier versions, that would be silly. I am however concerned that if I load a scene or figure in Poser 11 and not use any of the Poser 11 features I would expect it to work, at least in the version where it was first created.
I have been a Poser user for many years and I would like to see it prosper so I am not saying this to start any software wars and if someone with Poser 11 proves that changes do not have the effect I will be more than happy.
DAZ Set me off with that newsletter first thing this morning (like a drug dealer dangling the drug of choice before the addicts eyes and telling him he will never again get it) and i think it is now time to cancel that newsletter too.
Time to distance myself for a while.
As far as I know, the only reason Poser shows that "new version" message is because of the version number right at the top of the file header. You can open the file in a text editor and change that single number, and Poser will no longer show the message. Anybody can do it.
But if there is some kind of kink in P11 that makes things incompatible with previous versions that is besides the obvious new features like unimesh skinning, then it's probably something that should be reported to SMS so they can fix it.
Ken, there's a post at Renderosity in the forums by Cage about the change from ValueParms/TargetGeom in Poser 11 changing his extensively modified and morphed figures making them incompatible with older versions.
The truth is this was a much needed correction, and makes our lives easier and better, but in the case of extensively altered old figures, which most users will never see, there can be incompatibility issues.
The casual user will never experience it.
Thank you for the clarification, I was unable to test in Poser 11 but it was a concern if I decided to upgrade. I was am not technical enough to understand fully the implications, just shows the old adage is true, I had just enough knowledge to be dangerous.
Yeah, sometimes we techno geeks give out just enough information for the casual user to get concerned about things that just don't affect them.
You may bump into it if you load an old, heavily morphed figure you saved years ago and then re-save the scene in P11. But, the odds are very long that you'll see the problem at all, and then it will only matter if you try to re-load that scene in an old version of Poser.
If the issue only happens when people get older (heavily customized) models, load them into P11 and re-save, then that means they already have P11. Why would they want to use the item in older versions? P11 has so many improvements that I never want to run older versions - unless for product testing. It doesn't seem to be reason enough to avoid P11 to start with.
But by any means, it makes no sense to post such issues at RO or any other forum - they should submit it to SMS tech support. They are the only ones who can do something about it. Remember it is Chuck Taylor who is the new Poser product manager, and things have changed for the better at SMS tech support since then. Besides Larry Weinberg, I think very few others know Poser better than Chuck. DOZENS of new features and improvements present in the current P11 build came from my personal suggestions and requests, so I know they are listening. For instance, that new "rotation" brush from the Morphing Tool was my idea! ^____^
If the issue only happens when people get older (heavily customized) models, load them into P11 and re-save, then that means they already have P11. Why would they want to use the item in older versions? P11 has so many improvements that I never want to run older versions - unless for product testing. It doesn't seem to be reason enough to avoid P11 to start with.
But by any means, it makes no sense to post such issues at RO or any other forum - they should submit it to SMS tech support. They are the only ones who can do something about it. Remember it is Chuck Taylor who is the new Poser product manager, and things have changed for the better at SMS tech support since then. Besides Larry Weinberg, I think very few others know Poser better than Chuck. DOZENS of new features and improvements present in the current P11 build came from my personal suggestions and requests, so I know they are listening. For instance, that new "rotation" brush from the Morphing Tool was my idea! ^____^
HAHA!Well, welcome to the HW community! Here we support Poser and DS, and don't care which one you use. ^___^