elena_c opened this issue on Dec 14, 2020 Β· 20 posts
elena_c posted Mon, 14 December 2020 at 1:41 PM
Got this error when plugging an environment texture into the background in the latest Poser 12 build. This was not an issue with the previous upgrade. It occurred in a scene I was working on before the upgrade and in a new scene, no changes, where I just changed the background nodes to check this issue. The error message pops up a few times, and then Poser freezes and needs to be killed via task manager.
Anyone else also have this problem?
hborre posted Mon, 14 December 2020 at 3:29 PM
This has been reported in another thread.
seachnasaigh posted Mon, 14 December 2020 at 3:46 PM
I just started a render with a couple of 8192x2048 image maps with no problem. Some other factor must also be present?
Poser 12, in feet.
OSes: Win7Prox64, Win7Ultx64
Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5
randym77 posted Mon, 14 December 2020 at 4:37 PM
I just tried it. I get that error message when I use Import -> Background Picture, but not if I apply the texture in the Material Room instead.
But I get that error message in Poser 11 as well, when using Import -> Background Picture.
Rhia474 posted Mon, 14 December 2020 at 5:31 PM
It is present every time I use the Background node specifically.
Afrodite-Ohki posted Tue, 15 December 2020 at 4:24 AM
Rhia474 posted at 4:24AM Tue, 15 December 2020 - #4407553
It is present every time I use the Background node specifically.
Same here. I haven't attempted in other materials yet, though.
- - - - - -
Feel free to call me Ohki!
Poser Pro 11, Poser 12 and Poser 13, Windows 10, Superfly junkie. My units are milimeters.
Persephone (the computer): AMD Ryzen 9 5900x, RTX 3070 GPU, 96gb ram.
elena_c posted Tue, 15 December 2020 at 4:42 AM
I could futz around with the background node using Cycles environment texture without issue in the previous build of P12, even using 8k HDRIs. This problem only occurred in the new build.
Y-Phil posted Tue, 15 December 2020 at 5:06 AM
I am not sure to understand the problem, I mean: using P12, I've created a 16384x8192 jpg picture, with a vic4 character and one spot. Then, I have been able to use it as a background picture for P11 and P12. Could this be related to the quantity of RAM available on the graphic card?
π«π½ππ
(γ£ββ‘β)γ£
πΏ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
πΏ Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
πΏ Nas 10TB
πΏ Poser 13 and soon 14 β€οΈ
Rhia474 posted Tue, 15 December 2020 at 7:08 AM
Not a background picture. A picture using the background node specifically, using Cycles nodes. And yes, it only happened after the November 25th build.
Y-Phil posted Tue, 15 December 2020 at 7:46 AM
Oops sorry. Indeed, it looks like only standard Jpg pictures are supported bigger than 4096px, neither HDR pictures nor tonemapped Jpgs.
π«π½ππ
(γ£ββ‘β)γ£
πΏ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
πΏ Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
πΏ Nas 10TB
πΏ Poser 13 and soon 14 β€οΈ
Y-Phil posted Tue, 15 December 2020 at 7:58 AM
Luckily, there's BB's EnvSphere
π«π½ππ
(γ£ββ‘β)γ£
πΏ Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
πΏ Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
πΏ Nas 10TB
πΏ Poser 13 and soon 14 β€οΈ
elena_c posted Tue, 15 December 2020 at 9:55 AM
If you plugged in an hdr file like Rhia474 shows above, it worked before, so it's not the file format. It occurs when you plug in a Cycles environmental texture into the background node (using the mapping and texture coordinate nodes as above). I haven't tried other setups, so this may not be the only issue. Point is, the latest update broke this. It worked before.
Rhia474 posted Tue, 15 December 2020 at 10:58 AM
Yes, the envsphere from bagginsbill works. However. It is sort of embarrassing that their own native background node was fine before Nov 25 and is now restrictive enough that it requires messing with 4k hdri maps which are not that big. Why? Why break what worked? Can this restriction be removed please?
RedPhantom posted Tue, 15 December 2020 at 2:42 PM Site Admin
If nobody has, log it with support so thereβs a better chance of it getting fixed
Available on Amazon for the Kindle E-Reader Monster of the North and The Shimmering Mage
Today I break my own personal record for the number of days for being alive.
Check out my store here or my free stuff here
I use Poser 13 and win 10
Rhia474 posted Tue, 15 December 2020 at 3:26 PM
Yep, not at my compy atm ( work) but will this evening. Can't believe no one submitted this yet.
Rhia474 posted Tue, 15 December 2020 at 6:10 PM
Ticket submitted. We'll see.
RedPhantom posted Tue, 15 December 2020 at 6:40 PM Site Admin
I personally donβt think I should since I donβt own P12 yet or I would have.
Available on Amazon for the Kindle E-Reader Monster of the North and The Shimmering Mage
Today I break my own personal record for the number of days for being alive.
Check out my store here or my free stuff here
I use Poser 13 and win 10
ghostship2 posted Wed, 16 December 2020 at 11:36 AM
yes, this issue was also submitted by a beta tester two weeks ago. They are aware of the problem.
W10, Ryzen 5 1600x, 16Gb,RTX2060Super+GTX980, PP11, 11.3.740
Rhia474 posted Wed, 16 December 2020 at 5:40 PM
I was contacted by John from support for further information, so they're definitely working on it.
elena_c posted Thu, 17 December 2020 at 11:51 AM
That's good to hear. I'm working around it by touching the node, clicking away two error messages, then saving the scene and quickly exiting the material room before Poser freezes on me. It does what it should despite the error, so it's not like it's actually not supporting these images.