Hello, I'm muddling through my first from-scratch vehicle creation, and have reached an roadblock that I just can't seem to get around. I'm trying to put together the powertrain, and as far as I can tell I have all the required pieces in my .jbeam file (since this is an example car and very basic, I'm just putting everything into one jbeam file rather than breaking it out and using slots, etc.), however I cannot get it to put power to the wheels. I have the powertrain setup defined like this: "powertrain": [ ["type", "name", "inputName", "inputIndex"] ["combustionEngine", "mainEngine", "dummy", 0 ] ["torqueConverter", "myTorqueConverter", "mainEngine", 1 ] ["automaticGearbox", "myGearbox", "myTorqueConverter", 1 ] ["shaft", "myDriveshaft", "myGearbox", 1 ] ["differential", "myTransaxle", "myDriveshaft", 1 {"diffType":"lsd", "gearRatio":3.55} ] ["shaft", "myAxleShaft1", "myTransaxle", 1, {"connectedWheel":"FL"}] ["shaft", "myAxleShaft2", "myTransaxle", 2, {"connectedWheel":"FR"}] ], I believe I've defined all of the necessary components (see attached jbeam), and all the vehicle does when I hit the throttle is sit there, and the RPM goes up to ~1800 and stops, but no movement of the vehicle.
Hi, thanks for responding! I can't seem to find the UI App that you're talking about in the UI Apps tab, and the only one I have in the main menu is just the Powertrain one? (See pic). Google searching and Mod searching didn't seem to turn up anything, but I may not be searching for the right thing.
I have no idea what exactly is wrong, but there are 300+ errors in the console, and brakes don't work either, suspension is non-existent, and everything is a mess. Maybe don't use NBE, I'm pretty sure that is the reason why it's so messy. I would advise redoing it from scratch.
Hi, thanks for the feedback! I didn't create it with NBE, but I have been using somewhat of an unusual workflow, starting with a NASA program called OpenVSP, creating a volume tet mesh using Gmsh for the body, and then I wrote a parser in Python to convert it to beams/nodes. Suspension was figured out in Fusion 360 and put in by hand. It does look like I have some duplicate beams, I'll have to sort that out maybe with the Python parser. I was just ignoring the warnings for duplicate beams because it didn't seem like it'd affect the results, but let me know if that's a big no-no for other reasons, like it makes the vehicle unstable or something. Brakes are on the to-do list, and I've got placeholder beams in there for suspension, but I haven't changed their properties to be softer like real suspension. But yeah, it's kind of ugly right now. Any tips on "best practices" would be good. I know people seem to break out into separate jbeam files for suspension, powertrain, etc. but I wasn't sure my simple car warranted that, but if it makes other things clearer I should do that. Does anyone know how to get to the advanced powertrain debugger? I tried Ctrl+U and Ctrl+Shft+F which brought up some consoles I'd never seen before, but I wasn't able to find anything explicitly showing me how to debug the powertrain. That sounds key to me, then I could see what part of the powertrain is not transmitting power. Thanks! Bryan
I really thought you used NBE because of the node naming. And yeah duplicated beams duplicate the forces, so when you have so many of them then it will be super unstable once you add a proper suspension. And I still don't know what is wrong, the powertrain is fine, it just won't shift and won't rev high at all, as if there was some artificial limit in the transmission.
Thanks, I'll go through and get rid of the duplicate beams. Apparently my python script gets rid of any duplicates of "n1", "n2", but doesn't get rid of "n2", "n1". Hopefully that'll help a little, but I cannot for the life of me find any propulsion debug. The widget that appears in the lower left that shows damage, how do I get that to show up? Will that show propulsion? Thanks for the help all!
Powertrain is fine, I checked. Engine is also fine. It's either the transmission, or something physical in the hubs.
Ok, thanks. I went through and deleted all the duplicate elements (or I should say modified my bdf2beam python script to scrub them out). It didn't seem to have an effect, although there are way fewer warnings now. When you say something physical in the hubs, do you mean the beams that I created to put a node on the IB and OB side of the pressurewheel, or in the definition of the pressure wheel itself?