You can download it and see the current progress, but I warn you its not in a ready to use state I still have some work left to do
alright, but do the beams and triangle export already work? thats the main thing i want, also, you are doing a great job, just make the update great
I guess I was wrong, it's still doing it randomly. No errors that I can tell, it's just not saving the positions of the nodes. It also seems to be random, some nodes will move while others just stay put.
Beam exporting is almost done but triangle exporting is actually a different animal due to how Blender handles triangles. Triangles are defined by beams in Blender which is different from BeamNG which are defined by nodes, meaning having to do workarounds...
You mean as in the location of the file itself? I'd have to say no. I've tried saving the file imported & saving it as a new jbeam file & neither seems to work.
Hmm I'm not sure then. Does starting a new Blender scene help out? If not, if you don't mind sending me the .blend file as well as the JBeam file you are working on so I can see what the issue is (PM me if you want).
oh damn, well i hope you get it working, i know this is a dumb question and everyone hates it, but do you know when it could be released?
I'm having an issue with one of my cars. When I import the jbeam not all of the parts are there, no errors, but then if I try to export the jbeam it fails and I get an error. See, I was adding a new slot for a hood. I had blender open with the dae and the jbeam already imported. I moved some nodes to make room for the hood, then exported it. Then I pasted the code for my hood into the jbeam, deleted the jbeam in blender and imported it again. The hood successfully appeared so I moved the nodes where I wanted them. But on exporting to jbeam I received this error: Now if I import that jbeam file there are 2 slots that don't import, "ripper_steering_wheel" and "ripper_gauges". The steering slot is referenced in the error. I didn't change anything with those slots. Restarting blender didn't help. It only seems to be this jbeam file, other jbeam files seem to import all of their parts properly. I get the same error on exporting, if I import the problem jbeam to an empty scene with nothing else in it.
Not sure but hopefully within a month. I also need to do testing to make sure stuff is as bug free as possible and doesn't break and cause chaos
Thanks, I'll try to comb it over before I take up your time, though. --- Post updated --- It was indeed a syntax error, but in the slot above the steering slot, so not where I was looking. It was an extra } near the very end of the previous slot (which was still able to import into blender, btw). Thanks for pointing me towards the syntax. Is there any way the error report could more accurately point out syntax errors? Perhaps that's outside the scope of the plugin. Thanks again for your work on this, excited for the next update.
if you want i am available for testing, if needed, i will fill out a form for not spreading anything, i would love to test the jbeam editor and just have fun, it also increases my work speed, and probably yours too, so pm me (idk if you can) if you want me to test.
Nice you found the issue Should have mentioned this before, but we actually made a prototype VSCode JBeam Editor plugin which includes a JBeam syntax checker and also can visualize the JBeam part (no editing tho) https://marketplace.visualstudio.com/items?itemName=beamng.jbeam-editor In the future, the Blender Editor and the VSCode plugin are most likely going to be merged into one tool.
Appreciate it When the time comes to test, I could just make an announcement here and you and others that would like to test it out can simply just download the plugin from GitHub to test it out.
that would be great! i ofcourse want to help to make this the best it can be for modders like me, because i find making jbeam a hard task, but it did get easier with this, i just want the possibility to export triangles and beams, that all and it will come hopefully in early or mid january, just hit me up on discord if you want: saimonicl
Tried the VSCode addon, which sounds incredibly promising. I was able to pick the file association, but now it's stuck on 'Connecting to BeamNG', any ideas how I can fix this? interesting, the 3D preview works, despite it still trying to connect:
The "Connecting to BeamNG" message you don't need to worry about. The message goes away when you open the game and for now I believe just displays some JBeam statistics about the current vehicle in game.
