Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
センサー及び銃器を一括して横倒しにすればそのまま動作可能なはずです。ただし、オフセット座標は必ず合わせなければなりません。合わせなかった場合、命中率が低下します
search parameter table.
but, air drug change at Space Update is bad for long range.
GPS Position DiffとAltitude Position Diffはそれぞれレーダーがつながっている2軸のピボットの軸の交差点から、GPSセンサとAltitudeセンサの位置の差(単位はm)です。これを抑えて、設定値と組み込んであるセンサの位置関係を見直してみてください
GPS Position Diffと
Altitude Position Diffの設定方法がいまいち理解できません。
もしよかったら教えて下さいませんか?
m/tick ( = m/s/60 ) is the unit of velocity.
in progress
Ballistic computer maximum range is limited by it's cannon type(cannons maximum range). So no reason to extend range of it. Even if extended, the bullet would disappear before hitting the target.
Edit the property "Maximum Distance" to extend range of radar tracking.
I have tried all sorts of ways. I have tried putting all the sensors that are at the base of the radar, at the base of the gun as well and entered the same offsets present for the radar. Did not work.
I have tried connecting the ballistic calculator inputs to the sensors at the base of the radar and entered offset from the sensors, as well as offset from the gun. Did not work.
I have literally copied the same layout you have on the test bed and applied it to my ship, still did not work.
What am I missing here?
Just for the record, this is what I'm talking about when I talk about the gun making small jumps: https://youtu.be/2xmttsdFfyc
Yeah, sorry about the message yesterday. I got really frustrated after not being able to make decent progress and ranted in the comments.
It was not very nice of me.
With that said, I will stand behind my argument that I don't think you've tested this system on moving platforms before releasing it.
It works well enough on the ground, but as soon as you put it onto a ship, which always moves around, the experience is not great.
Thanks for the reply and the addon though. I will work on implementing my own radar tracking system instead.
First, sorry for reply TOO late.
My description is not good. no, it's too bad I think.
BUT
I have spent about half year, developing this system. I see nothing wrong with the users having to spend even 1% of that.
Much love, for trying and error users.
First the radar wouldn't turn (pitch & yaw) at all and it took me 2 hours before I realized anything below 80% sensitivity (I used 7 percent on the the original gun which I was trying to integrate with this) on the seat settings makes the input delay SOOOO long that it basically doesn't work at all.
Then once I figured that out, it turned out that you have to have the exact orientation of the pivot motors as the template build. Using an inverter to switch the pivot directions just made it not work in other ways. So I had to rebuild the gun to exactly match the template.
That was another 2 hours, but whatever.
It also turned out that you can't use velocity pivots for pitch. Otherwise the gun just continuously pithces around. Even though there is a setting for velocity and robotic pivots, you HAVE to have the yaw motor a velocity pivot, and the pitch motor a robotic pivot, otherwise it is messed up.
What's more, when the gun is locked on to the radar target, it keeps making these small jumps randomly. It doesn't stay fixed on the target.
I am so frustrated right now. It was supposed to be a simple plug and play module but there are so many things that are not explained in the description and the whole thing has clearly never been tested on anything except the template it was built on, at least nothing that moves that is.
By the way, even on the test bed; Switching the heavy cannon composite connection from radio, directly to the radar composite makes the aim go whack. Changing the lag to 0 does nothing.
And one last thing;
"As an example, if the radar is to spawn with the front side facing you as seen from the rear of the workbench"
Why would you describes it this way? In %99 of cases, why would anyone place the radar facing the back of the vehicle they are building?
"They can be placed anywhere as long as the merge is the same as the base of the radar's horizontal pivot."
What is "the merge"? You use it a number of times and I have no idea what it means.
God I am SO frustrated right now. Wasted HOURS on this thing.
I need to go calm down a bit.
seat and press "1" hotkey to make radar to tracking mode if no change to this vehicle.
I have issues with your creation on the latest version. I point the laser to the target vehicule, the turrets do not turn into the target. The firing button does work however. I think it has something to do with the radar controller
Not only this way, but also low pass filter to get target velocity.
These efforts allow target positions and velocities to be obtained with minimal time delay.
"Extremely high load" is caused by ballistic computer(not radar controller). ballistic computer do many times of trigonometric function and division etc... This is why this package consume so much resources of logic tick.
Second question, It's exactly as you say. I needed same tick sensor data for getting target GPS position. That's the simple way to delay data streaming.
Looking at the code, they all feed into LUA blocks, which from a brief check of a couple, I assume are all running the same code, outputting the same values? I'm hoping for something a little more compact - can this be run with a single radar, into one LUA block (which would save on that "extremely high load" you warn about by eliminating the same code running over the same numbers eight separate times)? Again: I may well be (and probably am) missing something crucial there. Also looks like there's a whole bunch of function blocks in there doing nothing but passing 'f(x)=x' from input to output.. is this just trying to get a delay into the input number?
Sure. But high speed rotation of turret may cause loosing rock-on of radar.
How did you have any idea how to make this?
You can change cannon type in microcontroller property. Choose "Rotary Auto Cannon" in drop down of "Cannon Type".
Yes it will be worked.