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.


Messages - Luca Giarrizzo

Pages: 1 ... 28 29 [30] 31 32
436
Hello David,

Thank you for reaching out to us.

In order for us to investigate this issue further, you can send the SBS files that appear to trigger the freezes, along with their dependencies.

To package all these resources, go in the Explorer panel in Substance Designer, right-click on your Package and select ‘Export with dependencies…’). We recommend checking the option ‘Build archive’ in order to create a ZIP file for simple transfer. This operation will only be possible for packages that you are able to open in Substance Designer.

As for sending us all these resources, Google Drive or WeTransfer links will work just fine for us.

We thank you for your time.

Best regards,
Luca Giarrizzo

437
Hello Atilla,

Thank you for your response and for providing these addtional details. Also, apologies for my erroneous inferences, you were right in pointing that out.

We had multiple reports of UI and graphics issues when the 3D View is set as fullscreen on a different monitor than the main Substance Designer window.

We were able to consistently reproduce unexpected behaviours with both AMD and Nvidia GPUs - although the symptoms differ between the two. We are actively investigating it, and will make sure get back to you if we need further information about your system, as you kindly offered.

Your help is appreciated! In the meantime, the 'solved' status of your request has been removed pending new information.

Best regards,
Luca Giarrizzo

438
Hello,

This is the thread for providing us with information about the apparent crash on startup of Substance Designer 2019.1.0 for users from China.

In order for us to investigate this problem, please send your log file. It is located in this folder:
  • [Windows] C:\Users\<username>\AppData\Local\Allegorithmic\Substance Designer
  • [macOS] Library > Application Support > Allegorithmic > Substance Designer
  • [Linux] ~/.local/share/Allegorithmic/Substance Designer/databases/thumbs.sqlite
You can attach the log file to a reply in this thread.

If possible, after a crash, please send the crash report by following the instructions in the prompt that appears when starting Substance Designer again. Make sure the 'Send additional information' checkbox is checked.
Provide detailed steps you took before the crash in the text input box.

Additionally, please provide the following information:
  • Is your computer reliably connected to the internet when starting Substance Designer?
  • Is the version 7.0.0 of the Substance Engine currently selected? You can find out about the current engine by pressing the F9 key, or in the 'Tools > Switch Engine...' menu;
  • Are your graphics drivers up to date?
We thank you for your time and help!

Best regards,
Luca Giarrizzo

439
We are happy to help!

We hope you can quickly get back on creating and having fun in Substance Designer!

Best regards,
Luca Giarrizzo

440
Hello David,

Thank you for the follow-up!

The default Library filters point to resources included in the Substance Designer installation package, and are relative to the installation path.
Specific user graph dependencies will be auto-saved alongside the SBS, and should be restored following the same procedure as explained in my previous message.

Indeed, please get back to us if you encounter filters that appear being automatically pointing to auto-save folders resources.

For the time being, I will mark this request as 'solved'.

Have fun using the Substance tools!

Best regards,
Luca Giarrizzo

441
Hello monongahelamonster,

We understand your frustration, and will be happy to guide you through quick steps to batch update your SBS files.

Powerful command line tools are included in the Substance Designer installation, which purpose is to help users automate and batch processes. In your specific case, you can use the 'sbsupdater' command line tool, located at the root of your Substance Designer installation folder.

To quickly get started in Windows, open the command prompt by pressing the 'Windows + R' keys, typing 'cmd' and pressing 'OK'. The Command Prompt will open.

Navigate to your Substance Designer installation folder by typing the following and pressing 'Enter':

Code: [Select]
cd <SD-installation-path>
Replace <installation-path> by the path of the Substance Designer installation folder.

From there, you can run the sbsupdater tool by typing 'sbsupdater' followed by a space and the appropriate arguments.
You can find a list of the available arguments and functionality by using the '--help' argument, like this: 'sbsupdater --help'.

Note: You can find the same list in the 'Substance Automation Toolkit' documentation, available here.



Now, to batch update your files, you can run a command that looks like this:

Code: [Select]
sbsupdater <folder-path> -r --output-path {inputPath}
This will look for all SBS file contained in the folder which path is <folder-path>, update them and replace the original versions.



We hope this was helpful, feel free to get back to us if you need further assistance.

Best regards,
Luca Giarrizzo

442

Hello CodeRunner,

Thank you for your feedback. Yours is a valid concern and the topic will be discussed internally.

You can follow up on fixes and features implemented in the future releases of Substance Designer by taking a look at the release notes, available here.

I will go ahead and mark your request as 'solved'.

Best regards,
Luca Giarrizzo

443
Hello Konrad,

Thank you for reaching out to us!

We understand your frustration regarding the new 'Tab' functionality in Function Graphs in particular.
We agree that giving users options is best in this case, and will look into implementing a toggle to turn the new 'Tab' key functionality on/off.

To follow up on features and fixes implemented in the next releases of Substance Designer, you can take a look at the release notes available here.

Have fun using the Substance tools!

Best regards,
Luca Giarrizzo

444
Hello tsukimiyiandrew,

Thank you for reaching out to us!

Currently, the naming of output exports is not part of the internal API, thus the built-in functionality is pretty much set in stone.

However, the code responsible for this functionality is already written in Python, and should therefore be quite straightforward to copy/paste into your code, and modify it to suit your needs.

You can find that code in the 'export.py' script, located in '/resources/python/sd/tools' inside the Substance Designer install location.

For your information, our team is currently looking into ways to make this customisation available in the sd.tools.export.exportSDGraphOutputs class, and make it follow the same naming scheme as currently implemented (i.e. $(graph), $(identifier), $(index), etc.).

To follow up on the fixes and features implemented in the next releases of Substance Designer, you can take a look at the release notes available here.

We hope this was helpful!

Best regards,
Luca Giarrizzo

445
Hello Vilém Duha O,

Has following the steps described in the thread linked by Daf57 solved your problem?

If it has, we will mark your request as 'solved'.

Best regards,
Luca Giarrizzo

446
Hello bbfizzle,

Thank you for reaching out.

With the 2019.1.0 update, we changed the way plugins are loaded in Substance Designer. You can now use the Plugin Manager, located in the 'Tools > Plugin Manager...' menu in the main top bar to load and unload plugins.

The 'Preferences > Projects > Python...' menu is used to point Substance Designer to your plugins folders. Additionally, you can also use the 'SBS_DESIGNER_PYTHON_PATH' environment variable.

For more information, please refer to the 'Scripting' chapter of the online documentation, available here.

Feel free to get back to us if you need further assistance.

Best regards,
Luca Giarrizzo

447
Hello CodeRunner,

After investigating further and consulting with our developers, we have additional details to provide. It appears the issue is also connected to the stage of converting (or casting) a float value to an integer.

While casting a Float to an Integer floors the value and allows it to be connected as an Integer to other operators and functions, it is still being processed as a Float, which are not meant to be used in the processing of Random Seeds.

For similar reasons, as Nicolas Wirrmann said, multiplications should be avoided in Random Seeds functions.

Therefore, please only use Integers from the outset in Random Seeds functions.

Best regards,
Luca Giarrizzo

448
Hello David,

Thank you for reaching out.

Please note that in order to restore a project from an autosave, you need to move the autosave to the original SBS file location, then rename it to the original file's name (see attached GIF). The original file can be deleted, or renamed to '<name>_original.sbs' for instance.

As a first step, please confirm you follow these steps when restoring from an autosave.

For your information, you can choose the auto-save time period, as well as the maximum number of files to be kept at all times, in the 'Edit > Preferences > General' menu (see attached GIF).

If these steps do not solve your problem, we will investigate further and ask you more details about your system and usage of Substance Designer.

Best regards,
Luca Giarrizzo


[Attachments]
DEMO_AutoSave-1.gif
DEMO_AutoSave-2.gif

449
Hello Labyrinthe,

First, please confirm your issue happens in Substance Designer, since you mention 'SP' in your post. If the issue is related to Substance Painter, I will move your post to the appropriate forum section.

Additionally, please share some screenshots that clearly show the unexpected behaviour and, if possible, the mesh file that displays in the way you describe.

Thank you for your time,

Best Regards,
Luca Giarrizzo

450
Hello

We will go ahead and consider our response was helpful and that this issue is now resolved.

Feel free to get back to us if you need further assistance.

Best regards,
Luca Giarrizzo

Pages: 1 ... 28 29 [30] 31 32