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 - llgarner

Pages: [1]
Between autosaves and actual saves, I am losing a lot of work time, maybe 15 min for every save. Plus with the autosave taking that long and happening at intervals, that means every 30min or so, I'm forced to stop for at least 10-15min. I have a huge workload and this starting to hurt my bottom line. If there's something I can do to speed that up, please point me to it.

Is it possible to change the UDIM tiles to have names instead of numerical output? And if so, will this get jumbled up like in my previous post about bad names when exporting?

Substance PainterSubstance Painter - UV Tiles - UDIM tile names on export
 on: September 24, 2020, 09:35:38 pm 
When I export my textures from Painter on a project that uses the new UDIM workflow, it seems to be regularly renumbering some, but not all of the maps, so that it's not exporting with the same file names each time. This makes iterating textures in the target app incredibly problematic: in my thinking, it should be able to overwrite the previous maps which I would then refresh in the app and have the results show, but instead, whatever new names/numbers Substance saves things out won't correspond to the originals, and so it requires either manually renaming all the newly output maps, or just replacing, manually, all the maps every time, a real time sink. Is there something stupid I'm missing here?

So... I needed to get my exact geometry back out of Painter, tried an export; for some reason it collapsed all the UDIM tiles in the exported mesh down to the first UDIM unit. Seems crazy to me that it would do that... am I missing something?

I  seriously need to talk to someone about billing/subscriptions. There are ongoing problems trying to bill for my subscription and there shouldn't be. l even started a whole new subscription upon someone form Allegorithmic's suggestion, and also paid for the perpetual license from the old subscription. Billing was changed to what I needed to change it to, and yet there still seem to be billing problems that aren't making sense. I need Substance, particularly Painter, for my day to day work and these kind of issues are causing some serious problems for me, and I need to get them sorted asap.

need to update billing info... where?

Like the subject said: I can start it, but if I use anything from the create menu at launch or close that menu and try ANYTHING, it crashes.

Just wondering if there is a comprehensive guide on the shelf system that is perhaps a bit more in depth than just the manual. I find the shelf system in Substance Painter very opaque and frustrating: inability to edit paths while a project is open seems very odd, and even thought I've pointed it at my own folders to use for shelves, it doesn't seem to update when i put new content in them. I'm just wondering if I'm completely missing something here, some paradigm/thought process on it that would make it make more sense? A little illumination here would be very appreciated. Thanks!

Besides acting very strangely when trying to add/remove shelves, would there be some reason that when I reorganize my materials in folder in Windows that SP should be seeing as my default shelf, it doesn't update? This is quite frustrating and eating into some serious work time this morning. Help, please? :)


Out of curiosity, and as a means of doing some seam overpaint to tweak a normal map (and some experimentation...), I sent my layers to Photoshop. Then, collapsed what was there into a single layer and saved it back out as jpg. When I imported that jpg into SP, it came in with this incredibly dark color shift, as though the program was reading the color space of the image wrong. I then tried it in different formats (psd, then tga), all with the same effect. The image is a normal map and looks fine in Photoshop, but every time I import any version of it into SP, there is a huge, darkening color shift. Any ideas on this? It makes some potentially powerful workflows rendered dead in their tracks.

Pages: [1]