Visual scripting interface does not start [Gelöst]

Schlagworte:
  • 2023-0-1

Hi
I have a problem on my workstation. Allplan Visual script interface does not start for me.
Reinstalling Allplan, CLEANSTD, CLEANREG, CLEANUP, CLEANVISGUI - nothing helps.
Any ideas what else to do?

Lösung anzeigen Lösung verbergen

Zitiert von: ChippyCat

Yes, I've tried to reset CLEANSTD and CLEANREG and then It could start again. But It's mean that all my setting will be default (setting font, dimention, anotation, .v.v.) so I have to setting them again.

Hey, you don't have to send private message to provide the data. You can upload it here directly. Perhaps, you have to rename it first to txt file, before you upload it.

I checked your file. I think, in you case, you need to reset the setting for Visual Scripting only, not for the whole Allplan. Next time you can try start CLEANREG then:
OK → No → select "VisualScripter" → OK

That will only reset the settings from Visual Scripting. You can check next time if it helps.

Product Owner API, Allplan GmbH

1 - 10 (14)

Zitiert von: Pero
Hi

I have a problem on my workstation. Allplan Visual script interface does not start for me.
Reinstalling Allplan, CLEANSTD, CLEANREG, CLEANUP, CLEANVISGUI - nothing helps.

Any ideas what else to do?



Version 2023 sometime doesn't start Visual sctipting.

Zitiert von: Pero
I have a problem on my workstation. Allplan Visual script interface does not start for me.
Reinstalling Allplan, CLEANSTD, CLEANREG, CLEANUP, CLEANVISGUI - nothing helps.

Which project country setting and Allplan language did you use? Did you get any information from Allplan trace window, when you click on the Visual Scripting? That will help us to reproduce that.

Zitiert von: ChippyCat
Version 2023 sometime doesn't start Visual sctipting.

Did you notice, when it always didn't work? or it is totally random?

Product Owner API, Allplan GmbH

Did you notice, when it always didn't work? or it is totally random?[/quote]

Visual scripting of version 2023 always doesn't start When I try to import the old privite setting ( Allplan 2022 ).

Country and language is "Slovenia". I tried changing the language to English, but the problem remains.
I am attaching some log files that are updated when I try to start Visual scripting editor.

Anhänge (2)

Typ: text/plain
828-mal heruntergeladen
Größe: 424,21 KiB
Typ: text/plain
748-mal heruntergeladen
Größe: 8,65 KiB

Zitiert von: ChippyCat
Visual scripting of version 2023 always doesn't start When I try to import the old privite setting ( Allplan 2022 ).

I'm not sure, what kind of old private setting you wanted to import??? Did you mean you can't open old script with the VS Editor?

Product Owner API, Allplan GmbH

Zitiert von: Xinling

Quote by Chip_pet_familyVisual scripting of version 2023 always doesn't start When I try to import the old privite setting ( Allplan 2022 ).

I'm not sure, what kind of old private setting you wanted to import??? Did you mean you can't open old script with the VS Editor?

I mean that When import the Privite setting of version 2022. I can not start Visual Scripting, get nothing when click to the icon visual scripting.

Anhänge (1)

Typ: image/png
53-mal heruntergeladen
Größe: 43,17 KiB

Zitiert von: ChippyCat

I mean that When import the Privite setting of version 2022. I can not start Visual Scripting, get nothing when click to the icon visual scripting.

I never used that function before... Have you tried to reset CLEANVISGUI after importing the private setting? Did the Trace Windows say anything?

Product Owner API, Allplan GmbH

Zitiert von: Xinling

Quote by Chip_pet_family

I mean that When import the Privite setting of version 2022. I can not start Visual Scripting, get nothing when click to the icon visual scripting.
I never used that function before... Have you tried to reset CLEANVISGUI after importing the private setting? Did the Trace Windows say anything?


Yes, I've tried to reset CLEANSTD and CLEANREG and then It could start again. But It's mean that all my setting will be default (setting font, dimention, anotation, .v.v.) so I have to setting them again.

Zitiert von: Pero
Country and language is "Slovenia". I tried changing the language to English, but the problem remains.
I am attaching some log files that are updated when I try to start Visual scripting editor.

Do you have the trace information when click on the VS button? Or can you also provide allplan_python.out? It should also locate unter <TMP> and it is log file for VS and PythonPart.

Product Owner API, Allplan GmbH

1 - 10 (14)