Fri, Nov 22, 1:08 PM CST

Renderosity Forums / Poser - OFFICIAL

All Forums

Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)

Poser Gallery - Poser Freestuff

Subject: Turning off "newer version" warning in pro 2014.

Mason41 opened this issue on Jul 18, 2016 · 8 posts
Back to Forum Print
Mason41 ( ) posted Mon, 18 July 2016 at 4:54 PM · edited Sat, 16 November 2024 at 3:20 AM

I have 2014 pro and poser 11 pro and use both versions and share the same libraries. Occasionally 2014 pro issues a warning when loading a scene or pose etc created in poser 11 pro that the file has a newer version. Is there anyway to turn this warning off in 2014? I use batch rendering and don't want that to jam up my production process.

SamTherapy ( ) posted Mon, 18 July 2016 at 5:02 PM

I'm not aware of any way to disable the message in Poser itself. The only way I know of is to edit the offending file and change the version number to one that doesn't give a warning, such as version 4 or version 6.

Coppula eam se non posit acceptera jocularum.

My Store

My Gallery

Mason41 ( ) posted Mon, 18 July 2016 at 5:21 PM

Yeah I was thinking of a python drag and drop script. I looked in the INI and found SHOW_PARSED_UNSUPPORTED_WARNING 1 which I set to 0 but that doesn't seem to have an effect.

arrow1 ( ) posted Mon, 18 July 2016 at 6:36 PM

I find if I make a genesis 3 figure in Poser Pro 11 and try to open it in Poser Pro 2014.Poser Pro 2014 crashes.There is some incompatibility there! Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.

hborre ( ) posted Tue, 19 July 2016 at 7:08 AM

Dimension3D's Runtime ZIP & Repair program will "fix" Poser Version within selected files.

putrdude ( ) posted Tue, 19 July 2016 at 3:02 PM

Maybe I'm missing the point, but can't you just load the P11 file in P2014, and save it again. Next time it should load, if I'm not mistaken.

hborre ( ) posted Tue, 19 July 2016 at 4:48 PM

That would correct issue for sure. But in the meantime you have to deal with annoying warnings every single time. And if you have 50 scenes, for example, the process becomes tedious.

putrdude ( ) posted Tue, 19 July 2016 at 5:01 PM

I'm used to tedious. Animation (to me) is an exercise in patience and tedium. You would only have to save them once, granted 50 scenes, but you would not be bothered again unless you made changes in P11. I have both as well, and I go back and forth too. It's a pain. P2014 has a much better library system IMHO. I can find things in it, that P11 seems to miss. Could be just me, but P11 library has stunk from day one.

Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.