Properties like "beamSpring", "beamDeform", "beamStrength", etc. should be added.

Let the user specify which vertex should be the refNodes.

export_jbeam.py:175 ,178, 186

Currently, BeamGen doesn't have an explicit name.

This operator is used to connect all selected vertices.
In mathematics, this is equivalent to complete graphs of dimension 3 : https://en.wikipedia.org/wiki/Dimension_(graph_theory)#Complete_graph

New name ideas :

• NodeConnect
• VertexConnect
• NodeSolidify
• VertexSolidify
• StructureSolidifer
• JBeam Solidifier

using bmesh in mesh operators is better as it more flexible and made to be used while the mesh is in edit mode (using bpy.types.Mesh could lead to desync)

I get an this error code every time i try and export a jbeam. ERROR: Mesh.update(): was called with invalid keyword argument(s) (calc_loop_triangles), expected (calc_edges, calc_edges_loose)

Installed Blender 4.0.2 with BlenderBeamNGExport 3.3, got the following error when exporting a mesh:

ERROR: Could not create export directories.

There is no option to import jbeam files as well.

It seems that the add on is checked and active.

Release date is somewhere in mid July

An info message in the status bar is appropriate for this.
Maybe we should notifiy the number of edges created : "BeamGen successfully created x edges."

We could make a menu category 'JBeam' and put it in there.

The user could be able to set the flexbody properties of a 3D mesh :

• Mesh name
• Flexbody groups
• Transform (loc, rot, scale)

The transform properties could be taken directly from the blender object properties.

We could use the blender collada operator to automatically export the meshes

The value defines the cost of the part.

Add per node naming, so that we can name the nodes properly inside blender, cause the default numbering isn't good enough.

The user should disable jbeam data per type on an object basisn but also on a scene basis.
Example : disabling col tris export on the scene side won't export col tris for the objects even if col tris is enabled object wise.

We need to add weight, material, friction, collision ... properties do each nodes

The cost field for a part should be optionnal, we should add a checkbox to enable/disable this.

The user could manage the slots directly from the UI, :

• object pickers for picking the slots
• set the slot names
• set the slot options

Should be

"nodes":[
	["id", "posX", "posY", "posZ"],
	{"group":""},
	["nl0",1.0,-1.0,-1.0],
	["nl1",1.0,-1.0,1.0],
],

Instead of :

"nodes":[
	["id", "posX", "posY", "posZ"],
	{"group":""},
	["nl0",1.0,-1.0,-1.0],
	["nl1",1.0,-1.0,1.0],
	],

Documentation : https://wiki.beamng.com/JBeam_Reference#quads
The user could choose between collision triangles or quads.

Currently, BeamGen generates edges even on already existing ones :

This is not the intended behavior, we should check if the edges we want to add are already existing.

It would be extra helpful, if vertices assigned to multiple vertex groups could be exported to multiple nodegroups.

https://www.mediafire.com/file/tj1s8zbd5sp6gav/Anderson_King_Coil-Over_Shocks.blend/file

https://www.mediafire.com/file/vdyy25cwi2zbdjo/Coil-Over_Shocks.blend/file

https://www.mediafire.com/file/igrfn4rcoav1x1a/King_Coil-Over_Shocks.blend/file

https://www.mediafire.com/file/0nlr031fjwq20hm/CRD.zip/file

https://www.mediafire.com/file/ihosjbndmloc4to/CRD_Blz_5.zip/file

https://www.mediafire.com/file/3p1devlqu764bqn/Elbow_Swaybars.zip/file

https://www.mediafire.com/file/jtn09zkuep22e93/Wolverine.blend/file

(sighs) I've been searching YouTube everywhere for a full tutorial which shows me step by step how to mount all coil-over shock packages properly on every last Monster Jam chassis there is for BeamNG thus far; & even today, I find none. I see no member of Beam-Monsters either able or willing to help me, nor do I see myself accomplishing this task at all without help.

In a special competition I had in mind for BeamNG, there was a rule regarding suspension packages. As for any Monster Jam truck featuring coil-over shocks, the coil-over on every last corner of any Monster Jam chassis [produced for BeamNG] belongs in between its assisting nitrogen bypass shock & any sway bar on the front or rear. Sadly, the only coil-over shock packages properly mounted on any Monster Jam chassis produced for BeamNG are those on the rear of both CRD & CRD 3.0 chasses; & to me, that is absolutely unsatisfactory.

If there is indeed a full tutorial which shows me step by step how to mount all coil-over shock packages properly on every last Monster Jam chassis produced for BeamNG, I'm looking for it. Some other changes are in order as well.

Since neither Anderson shock package is properly placed on either differential's mounts, that's why the Anderson sway bars belong in the Adjustable Addons pack; but I see no way to move them from one pack & place them in another. A parsing error prevents me from importing the Anderson nitrogen shocks & the Bigfoot X Cantilevers into Blender as well, & I'm not sure why.

As for the King coil-over shocks, moving each one's hose is the tricky part.

I'm yet to find out how to apply textures to certain items, such as the elbow sway bars (Anderson & CRC (for the CRD chassis)).

And these are .dae, .jbeam, & .json files we're dealing with.

Shown here is how all coil-over shock packages are properly mounted on a CRD chassis; but on BeamNG, that ain't the case at all.

It was done in real competition.

It was done on Rigs of Rods.
https://www.mediafire.com/file/gdfkof284mln3vo/WOLVERINE.mp4/file

But why can't it be done on BeamNG as well?

version not defined in export_jbeam.py

Currently the user is notified the selected mesh is incompatible with a checkbox :

In terms of UI, this is wrong. A more appropriate way to handle this is by showing a label with an error icon.

The user should be able to enable/disable node groups export.

If the JBeam file already exists and is overwritten, the old one is lost. Something we could consider is backup the file before it is overwritten. Example : a JBeam file is overwriten but the export script has an exception, the result is a partially incomplete/broken JBeam file.

One possibility is to increment the extension like blender does :

These backup file could be stored in a folder called 'JBeam backups' in the export folder path.

Properties like "dragCoef", "groundModel", etc. should be added.

See https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Python_API/Addons#Naming

Currently, there are warnings in the system console :

New class names proposition :

I keep getting the same error message when I try to export