the reason they are missing is that the rangers only update a certain number of times a second. Maby a hispeed checking option for them? it would increase the strain on yoiur processor but give a better chance of tracking hispeed objects?
Ok, so I've managed to get a couple of boxers to run. They chug along, quite literally, all night long with no problem. They probably have 500KG's of flyweight on them, so the LOW(50-150) RPMs dont bother me any. I go to build a high-RPM engine for use in powering a cargo truck, which is currently propelled by the magicness motor in the GMOD wheels. I get it built, everything rotating is EXTREMELY light and very well balanced(no shaking whatsoever on starter motor, approx 800RPM), all should be good in the hood. I rig up the ignition(see below) and spin it over, it fires once, twice, then starts missing. Ittl maintain about 100RPM average, while firing on maybe two out of 10 revolutions. This tends to make the pistons wig out and one of them will try to move in the same 'bore' as the other. Quite amusing to watch as it still runs like this.
My ign. circuit:
Ranger(reading off crank trigger) ----> B Less Than gate A <--- Constant Value
If the less than gate returns a 1, the thrusters fire. A 1 is returned when the dist value from the ranger is less than the constant value. Extremely simple, does work, but doesnt like high RPM or the crank trigger at or before TDC. Tends to kick back when positioned there and run backwards. Runs best when timing is retarded about 15º from TDC. I may have the inputs backwards here. On the engine, they're correct.
My kill switch, sometimes used, has no effect on RPM:
Numpad input(toggle) ---> AND <--- Less Than gate
If AND returns 1, thrusters fire. Thrusters are no longer connected to Less Than, that goes into the AND.
Any help is appreciated and any circuits presented will be tried, Thanks a bunch.
Wait, what? A sig? nothing to see here, move on along.
the reason they are missing is that the rangers only update a certain number of times a second. Maby a hispeed checking option for them? it would increase the strain on yoiur processor but give a better chance of tracking hispeed objects?
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Super Easy Wire Download
I've managed to get the RPM into the useable band, 400-600. I achieved this by paperweighting and nogravity-i-fying the rotating assy. It still misfires like mad, but it is useable. It's running as if it's got a governer or something. I just checked my wiremod, there's no hi-speed sampling option. Off to the requests forum! If anyone else knows of a way to read the crank trigger faster, please post such information. Dammit I wish I knew lua better than making minor wep tweaks...
Wait, what? A sig? nothing to see here, move on along.
i meant that i would add a hispeed sample. not right now but once i get home.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Super Easy Wire Download
Couldn't you just stick a gyro on the wheel instead and use precise triggering?
the gyro updates at the same rate as the ranger so that would miss aswell.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Super Easy Wire Download
Bookmarks