Thorsten Kaufmann
Thorsten Kaufmann
We want these guides and docs to be uptodate and up to ASWF standards ahead of time to ease integrating and graduating the project.
This PR adds support for setting of nested prompt decorators and for 3rd party prompts by adding an option to only set the prompt as an environment variable so it...
There is a regression that was introduced by #1176 The nested `Get-ChildItem` call fails with an error if the Variable does not exist. Old behaviour restored without reverting the fix...
Windows currently does not detect the shell it is being run from and uses `cmd.exe` if not explicitly overriden. See https://github.com/nerdvegas/rez/blob/1ecc85f638d11d70ed78d4bd9c5cdc6f32ac58c4/src/rez/system.py#L81 **Motivation** I think the original implementation predates PowerShell and...
The current implementation to set the prompt on windows creates a custom prompt function. This overrides existing prompt functions a user may have set including 3rd party prompts like https://ohmyposh.dev/...
I have not looked deeper into this, the old version we had deployed (2.88.4) seemingly creates the env variable whereas the current release fails with a PowerShell error. https://github.com/nerdvegas/rez/blob/d4b303f8a23d2d190d4d48183c6ae51a906e98cc/src/rezplugins/shell/_utils/powershell_base.py#L256 Looking...
We should add a deprecation notices for rez-bind in general, and particularly for --quickstart and windows. Another new user ran into this today. Following the Getting started guide on windows...
When adding the -ExportPath parameter i get the following error: ``` Exporting report into speedscope format.MethodInvocationException: C:\Users\*****\Documents\PowerShell\Modules\Profiler\4.0.0\Export-SpeedScope.ps1:37 Line | 37 | $destination = [Profiler.SpeedScope.SpeedScope]::Export($expo … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Exception calling...
Hi, i just gave compiling Aurora a first try on Windows using VS2022. I followed the step by step tutorial and building went fine. I can also load Plasma fine....
Importing files with explicit normals (in this case from CAD data) discards (or recomputes) normals
**Describe the bug** When importing geometry originating from CAD the included normals seem to be discarded and that creates very visual shading artifacts. If i import or load the same...