Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - pbowmar

Pages: [1]
1
Hi,

the Painter RPM installer is tagged as Not Redirectable, meaning someone must be root to install it to /opt then it needs to be copied from there to the actual install location.

Curious why it's restricted like that? Would be very helpful and convenient to be able to install directly to the install location without needing root.

Cheers,

Peter B

2
Hi,

Exporting EXR direct from Alchemist, it appears that BaseColor (sic) is having a gamma 2.2 applied? How does one turn that off to get proper linear colour space exports?

0.5.4 Linux

3
Hi,

Going through the Wood Plank tutorial. In the Tiling section, if I make a mistake rotating the manipulator (easy to do, the mouse movement to rotate isn't super intuitive IMO) and I Undo, the entire Tiling Layer is removed and I have to restart all the Tiling work.

Ideally, it would undo the last move of the manipulator.

0.5.4 Nacho

Linux (openSuse 42.3)
OpenGL renderer string: GeForce GTX 960/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 410.78

Cheers,

Peter B

4
Hi,

Where can I find the docs for command line option --enable-remote-scripting?

The other command line options make it tantalizingly close to being able to launch SP from DCC apps like Houdini and the --enable-remote-scripting seems like exactly what I need to then set up the rest.

However, no idea how to even try it :(

Linux btw using latest SP

Cheers,

Peter B

5
Hi,

So, Painter 2017.2 had the usual "missing dependency for libtiff.so3" which I just ignore with --nodeps on the RPM command.

However, 2017.3 has a huge new list:

/home/pbowmar/Downloads> sudo rpm -Uvh unsigned_Substance_Painter-2017.3.0-1837-linux-x64-standard-full.rpm
error: Failed dependencies:
        libQt5Charts.so.5()(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Charts.so.5(Qt_5)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5DataVisualization.so.5()(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5DataVisualization.so.5(Qt_5)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Location.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5MultimediaQuick_p.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Positioning.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Purchasing.so.5()(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Purchasing.so.5(Qt_5)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5QuickParticles.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5QuickTest.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Scxml.so.5()(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5Scxml.so.5(Qt_5)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libQt5WebChannel.so.5(Qt_5_PRIVATE_API)(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64
        libtiff.so.3()(64bit) is needed by Substance_Painter-2017.3.0-1.el6.standard.full.x86_64

If I ignore the deps as usual, I don't get missing libraries when I run "ldd" like so:

/opt/software/allegorithmic/substance_painter_2017.3> ldd Substance\ Painter
        linux-vdso.so.1 (0x00007ffed61f4000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9f969c8000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f9f967c0000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f9f965bc000)
        libQt5Svg.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Svg.so.5 (0x00007f9f96d63000)
        libQt5Xml.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Xml.so.5 (0x00007f9f96d21000)
        libembree.so.2 => /opt/software/allegorithmic/substance_painter_2017.3/././libembree.so.2 (0x00007f9f96241000)
        libQt5QuickControls2.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5QuickControls2.so.5 (0x00007f9f96d08000)
        libQt5QuickTemplates2.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5QuickTemplates2.so.5 (0x00007f9f96c21000)
        libQt5QuickWidgets.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5QuickWidgets.so.5 (0x00007f9f96c0d000)
        libQt5WebSockets.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5WebSockets.so.5 (0x00007f9f96213000)
        libQt5XmlPatterns.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5XmlPatterns.so.5 (0x00007f9f95e2e000)
        libQt5Quick.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Quick.so.5 (0x00007f9f959ee000)
        libQt5Qml.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Qml.so.5 (0x00007f9f955ab000)
        libassimp.so.3 => /opt/software/allegorithmic/substance_painter_2017.3/././libassimp.so.3 (0x00007f9f9425f000)
        libQt5OpenGL.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5OpenGL.so.5 (0x00007f9f941fb000)
        libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007f9f93f7c000)
        libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f9f93cd8000)
        libQt5Concurrent.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Concurrent.so.5 (0x00007f9f93cd0000)
        libsubstance_linker.so.1 => /opt/software/allegorithmic/substance_painter_2017.3/././libsubstance_linker.so.1 (0x00007f9f93a5b000)
        libsubstance_sse2_blend.so.1 => /opt/software/allegorithmic/substance_painter_2017.3/././libsubstance_sse2_blend.so.1 (0x00007f9f937bb000)
        libQt5Network.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Network.so.5 (0x00007f9f93648000)
        libssl.so.1.0.0 => /opt/software/allegorithmic/substance_painter_2017.3/././libssl.so.1.0.0 (0x00007f9f933d2000)
        libcrypto.so.1.0.0 => /opt/software/allegorithmic/substance_painter_2017.3/././libcrypto.so.1.0.0 (0x00007f9f92f7e000)
        libQt5Widgets.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Widgets.so.5 (0x00007f9f928af000)
        libQt5Gui.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Gui.so.5 (0x00007f9f922c3000)
        libQt5Core.so.5 => /opt/software/allegorithmic/substance_painter_2017.3/././libQt5Core.so.5 (0x00007f9f91d26000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f9f9199d000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f9f916a0000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f9f91489000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f9f910e6000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f9f96be5000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f9f90ecf000)
        libGLX.so.0 => /usr/lib64/libGLX.so.0 (0x00007f9f90c9e000)
        libGLdispatch.so.0 => /usr/lib64/libGLdispatch.so.0 (0x00007f9f909d0000)
        libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f9f907cd000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9f904bd000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f9f9017e000)
        libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f9f8ff6c000)
        libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f9f8fcfd000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f9f8fadc000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f9f8f8d8000)


which is great I guess and Painter seems to run OK.

So.... why the long missing deps list?

Suse 42.3 btw. :)

Cheers,

Peter B


6
Hi,

I've searched the forum and Googled, can't come up with the answer.

Basically I want to export each layer with its transparency (presumably in the Alpha of the exported layer but separate would be acceptable if needed) so I can recombine the layers dynamically in the renderer.

Simplest example: Fill Layer (set to solid Blue)
on top, a regular layer with some (let's say Red) paint strokes.

When I export, I want the Fill Layer (and all its channels) separate from the Paint Layer (and all its channels) with the Paint Layer having an Alpha (or whatever) I can use to 'composite' the Paint Layer over the Fill Layer, in my shaders.

I can't for the life of me figure out how to do this :(

Obviously, what I see in Painter may not match my composited image if Painters "blend mode" math doesn't match the math in my shader, but that's OK, that's my problem :)

3DCoat does this easily when you export to PSD. Painter seems to put the _channels_ in the PSD layers, not the _layers_ as you'd expect.

2.5.3 Linux

Cheers,

Peter B

7
Hi,

Now that Painter and Designer are available for Linux (yay!) curious if B2M might be coming too?

Cheers,

Peter B

8
Hi,

I'm trying to run the demo of the new Designer 5.5 on Linux. Painter 2.2.0 works fine (except non-threaded baking, but that's a known issue) but trying to install Designer fails with:

error: Failed dependencies:
        libcuda.so.1()(64bit) is needed by Substance_Designer-5.5.0-1.el6.standard.full.x86_64
        libnvcuvid.so.1()(64bit) is needed by Substance_Designer-5.5.0-1.el6.standard.full.x86_64

I assume this means I need a newer/different Nvidia driver install? Or is there a path missing to find it?

I'm on Suse 42.1 however that's very close to a RHEL 7+ and all major apps work fine (Houdini, Nuke, 3DCoat, Sub Painter 2.2.0 etc) so hopefully I'm just missing something obvious :)

Cheers,

Peter B

9
Hi,

I believe you might already be aware but baking of the AO and Thickness maps is single-threaded on Linux at the moment.

As requested the log is attached!

2.1.0 Linux

Cheers,

Peter B

10
Hi,

I fully realise UDIM is a work in progress, great to see it getting started!

One big thing I just noticed is that if you have multiple materials _and_ UDIMs, the TextureSet names get messed up and it becomes very hard to export the textures back out and match them with the input.

I've attached an example.

-import with Create UDIM turned off, you get (correctly) "sensor_pods_SubD" and "sensor_pods_noSubD" but with clashing uvs so you can't paint on it properly. However, TextureSet names are valid
-import with Create UDIM turned on, you get (correctly) 4 texture sets, but they are named "1001", "10011", "1002", "10021" making it virtually impossible to know where they came from or how to export them.

I would expect to see: "sensor_pods_SubD_1001", "sensor_pods_SubD_1002", "sensor_pods_noSubD_1001" and "sensor_pods_noSubD_1002" then it would be fairly easy to re-export.

I export via scripting, not via the Exports panel, however using the Exports panel, I would expect to be able to control the formatting of the UDIM part as well. In my studio that is separated by a period (aka full stop) like so:

materialName.UDIM.exr

for example.

However I have seen other places use underscores. So, I think user-control (with savable defaults) will be needed here.

Cheers,

Peter B

11
Hi,

Thanks for the scripting interface, very useful!

Unfortunately, the alg.mapexport.documentStructure() doesn't include the "Additional Maps" which would be very useful to be able to export as well. My shaders could use thickness, curvature and other things to supplement the painted maps with procedural stuff.

I tried "manually" exporting them via alg.mapexport.save() but even trying different naming combinations I couldn't get an image to export. Rather, I got a black image.

2.1.0 Linux.

Cheers,

Peter B

12
Hi,

So happy to have the Linux version. Super fast and easy to work with!

I have a few small observations/suggestions. Nothing that stops you working but since I'm sure Linux will be the platform chosen by some larger VFX studios, these might help smooth things a little.

  • How will floating licenses be handled? Most VFX studios cannot access the internet due to Marvel/MPAA security audit requirements
  • Even for smaller studios who are not encumbered by those restrictions, it would be nice to be able to specify the directory that contains the license file(s)
  • The actual executable contains spaces. I know, I know, that can be handled but it's non-standard on Linux  :)
  • Most larger studios will have multiple versions installed and available concurrently. It's great that the Substance_Painter_2 subdir is fully (except the license) self-contained, that makes it super easy to deal with. Please don't change that :)
Like I said though, small stuff, the speed and stability on Linux are fantastic.

Cheers,

peter B

13
Hi,

Scripting is awesome! However, I can't figure out how to refresh/reload a script without quitting Painter (2.0.5) so iterating/testing the scripts is very slow :(

If I have missed something, please do let me know!

Cheers,

Peter B

14
Hi,

I'm attempting to write an auto-exporter for Houdini from Painter so I can have a one-click export from SP2 into Houdini as RAT format (and have Houdini's IPR re-render using the new textures automatically too) but I need a little help with the scripting :)

First, any chance of industry-standard Python 2.7 (or 2.8) being added for scripting? All DCC apps on the VFX side use Python (Maya, Houdini, Nuke, Modo, Mari, etc) as the common language.

However, I realise that might be a longer term goal.

So there is JavaScript and QtQuick. Cool... but some "drop in and work" examples would be amazing. I haven't used JS for over 15 years, and I have no idea what QtQuick is. I'm sure I can figure it out but time is very limited for these types of projects.

Is there an example that:

On Export, takes the saved file paths and then runs a Subprocess that (let's say) renames the files, or copies them?

I could take that boilerplate and easily add the other stuff I needed rather than having to start learning new languages/libraries :)

The Shader docs have 3 helpful GLSL working examples, basically something like that but for Plugins would be amazing.

For those that haven't discovered it yet, the only place I've found docs on the plugins is from within SP2's Help menu.

Note: I've tried the "dock.qml" example, and nothing shows up in the Plugins menu...

Cheers,

Peter B

Pages: [1]