[3DCoat 2024 development thread]

Also I'm having an issue with the new Edge Radius `R` hotkey. It weirdly overwrites my other R-keys. Example: I had Alt+R assigned to Reset Axis command of the Transform tool option, in the latest versions it stopped working, but instead Edge Radius is changing. And I can't assign any R-hotkey (+Ctrl/+Shift).

Attaching a video. Edge Radius is set to 0. I try using my Alt+R key to reset axis, instead Edge Radius is changing to 165. Then I reassign the function to Alt+E and it works. And then I try to assign it back to Alt+R or any other +R key but the prompt "press any key" doesn't go away until I cancel it with Esc 

 

[3DCoat 2024 development thread]

Thanks for fixing the issue with .changeParent() Python method

Would it be possible to add "changeIndex(self, newIndex=Int)" method for SceneElement?

[3DCoat 2024 development thread]

I'm having an issue with a simple Python script with the latest beta (haven't tried the previous versions): the inputs seem to be correct, there are no errors but what I expect to happen (parents change) simply doesn't happen. I posted on Scripting subforum but I don't think a lot of people go there, could you please tell me what am I missing?

 

[changing parent with Python: nothing happens?]

First of all, it's awesome to see Python implementation in 3d Coat — it's so, so so much easier to dive into for mere mortals than AS and C.

I'm struggling with something: I'm trying to change parent for selected volumes from Root to an object with index 0 and while the console prints out correct values nothing happens in the scene: the parents don't change. My scene consists of 4 simple sphere volumes, two bottom ones are selected (selecting one doesn't make difference)

Code:

import coat

def main():
	root = coat.Scene.sculptRoot()
	new_parent = root.child(index = 0)
	selected = []

	def walker(el):
		if el.selected():
			selected.append(el)

	root.iterateVisibleSubtree(walker)
	print(f"selected elements: {selected}") # correctly outputs coat.SceneElement objects

	for el in selected:
		print(f"changing parent: {el.name()} from {el.parent().name()} to {new_parent.name()}") # prints out correct names
		el.changeParent(newParent = new_parent) # nothing happens
			
main()

Please let me know what am I missing.

Thanks!

[3DCoat 2024 development thread]

I think Circle Lasso and Ellipse Lasso stroke modes don't work with Voxel Hide :

 

 

[Python scripting support?]

Answer from Andrew:

Quote

We plan to make python scripting as well and we are working over it, I feel it is important.

so hooray I guess  

[Adding scripts as menu items in 3DC 2022]

Ok got an answer from Andrew: the path in the .xml Command tag should be relative to the 3dc Prefs folder. In V4 it's

<Command>script:Scripts/ExtraMenuItems/scriptName.cpp</Command>

and in 2022 the prefs were moved deeper:

<Command>script:UserPrefs/Scripts/ExtraMenuItems/scriptName.cpp</Command>

 

[Adding scripts as menu items in 3DC 2022]

Aha, works this way, thanks. I have 20 scripts to install so running them one by one for them to work in the menu seems annoying  seems like a feature digress

[Adding scripts as menu items in 3DC 2022]

23 minutes ago, Carlosan said:

As example i was testing this old V4 script, and it works without troubles

 

Hm, it doesn't for me. Could you please post the paths you're using? Here are mine:

 

When I run the script:

[Adding scripts as menu items in 3DC 2022]

1 hour ago, Carlosan said:

Hello

Better to ask Andrew.

I am shotting in the dark: try edit current room. I guess you have to add it to the text of the menu scripts.

Thanks, but it seems that editing the menu script won't help: there are no "commands" unless I'm missing something. Everything is being called via menu_item() function... Even the recent scripts list calls for a recent scripts menu item:

 

When you say "Better ask Andrew" do you mean by writing to his email? I imagine he gets 10000000 messages a day lol

Thanks

[Python scripting support?]

in the 3DCoat-2022\UserPrefs\Scripts\Python folder of the 3DC installation there are 3 simple test py scripts.

Does this mean that Python support is coming for scripting?

Is it usable already?

I find AngelScript extremely confusing and limiting for non-developers and Py would be a great addition to it or change from it.

[Adding scripts as menu items in 3DC 2022]

Hello, I'm moving to 2022 and I'm trying to bring my scripts from V4 to 2022.

In V4 I would have a \ExtraMenuItems folder with a bunch of .xmls with MenuPath, MenuItem and Command tags to define the name, menu and the actual script that's going to be used when the command is selected.

I copied the folder to the \Documents\3DCoat\UserPrefs\Scripts\ExtraMenuItems\ and the scripts appear in 2022. However non of them works, I'm getting "Nothing was built in the module" error. If I run the script via Scripts > Run menu they work fine. Should I change anything for the scripts to work from the menus?

Thanks

[3DCoat 2024 development thread]

On 11/28/2022 at 9:43 PM, Andrew Shpagin said:

Send me scene example to andrewshpagin@gmail.com (regarding export)

Sorry for the false alarm: after rebooting the PC export works. Didn't expect this to solve the issue...

(Airbrush still freezes on Invert though)

[3DCoat 2024 development thread]

Hello, does exporting works for you guys? I just installed the 2022.52 (Win10, 8c Ryzen, 64gb RAM, 2070S) and every time I try to export a +/- dense fbx (>300k polys) 3dc crashes (shows a window "the program became unstable and will crash"). If I save the scene and open it in 4.9.72 it exports fine. Exporting obj/collada exports broken geometry (floating parts of the original object).

Also Airbrush in Invert Mode freezes the 2022.52.

Anything I could try..?

[Is it possible to browse the sculptree with up and down keys? by kritskiy]

13 hours ago, PabloAB said:

This script is extremely useful and works fine, but sometimes the select_next.spp (Down) option doesn't work. 3DCoat 2022.34.
when it reaches the first layer it does not go down.
On intermediate layers it works fine.

it seems to work fine for me (2022.29)

do you get any errors..?

[3DCoat 2024 development thread]

29 minutes ago, milhouzz said:

you can hold alt and move...it s not ideal but its working ^^ still hope they will fix this

oh, thank you!

I noticed that the issue is persistent through a lot of operations. If I move with G and click to release the object or rotate the object, clicks will be also passed through

[3DCoat 2024 development thread]

Hello, in both stable and latest beta, using the gizmo to control the Stencil size/location/rotation passes through mouse clicks. Here on the video I'm scaling and moving the stencil but geometry behind it is affected. In V4 operating this gizmo wasn't passing through clicks.