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
... I feel stupid...
I look forward to the magnitude-less version as it's the style I've been using up until this point.
Upon playing around with the idea, I've decided to implement your suggestion :P
The magnitude-less vector is much more useful for my artificial horizon, so I have already implemented it there. I figured I might as well implement it in this one as well. I will update it soon.
Yes, on the timer there is a check box to turn off the timer noise. See time stamp 2:18 in my video :)
"Also, wouldn't increasing the max speed make the problem worse?"
Yes, I misspoke.
However, I am not interested in discarding information about magnitude. I might go back and add a toggleable function. Depends on how much work it is.
Again, I'm not suggesting that your way is "wrong", just that it differs from my expectations based on other such displays, and I'd love to have the option. And if I'm missing something here, please let me know.
Also, wouldn't increasing the max speed make the problem worse? The deflection of a small sideways velocity would be even less.
In the video around the 2:41 you can see the debuging output of the program. Is the program reporting any errors? If so, please take a screenshot and leave a link here :)
Also check ownership on all your blocks.
Have you started the timer?
Also sometimes LCDs bug out and you need to hold alt, look all the way right, then all they way left, and then recenter and the LCD screens will update.
Have you started the timer?
From google "translite" as you spelled it:
"let me fuck you understand or not , google translite to help"
I'd prefer you keep all fornication to yourself.
"Translited" your other message as well:
"pindos"
So hurtful...
Don't even bother commenting here if you are going to be belligerent.
Hope you enjoy :)
@Clanner Jake:
This would be quite a sight :)
@tomkrist:
Open a program block in the terminal. Click the workshop button bottom right.
"I'd think you would just normalize the velocity vector"
No. That removes absolutely all visual data about the magnitude of the speed.
"take its angle against the normalized facing vector in pitch and yaw, and use those angles to display the crosshair. If the velocity vector has zero magnitude, you'll have to pick a direction arbitrarily"
You don't even need to touch angles at all. Picking a direction arbitrarily is a terrible idea.
" I'd love to see a true vector indication using it"
From the description: This code creates a colored graphical representation of your velocity vector and displays it on a screen
Again let me state: This code presents a 2-dimensional representation of a 3-dimensional velocity vector. The length from center to any point along an axis is a vector projection of that velocity onto that axis.
"Could you make a version of this that actually shows you the *direction* of your velocity vector?"
It already does. If you are moving right the indicator is along the right axis. If you move down it is on the down axis. If you move forward it is green. If you move backwards it is red.
"yours shows relative velocity along each axis, which is not the same thing"
It is absolutely the same thing. The position on the vector on the screen is a two dimensional projection of the three dimensional vector.
"(and is less useful if you're moving slowly, since it will always appear that you're moving "forward" even if you're travelling at 90 degrees from your facing direction."
Increase the resolution and the max speed then. It will make the code more sensitive to tiny movements.
To do that, I'd think you would just normalize the velocity vector, take its angle against the normalized facing vector in pitch and yaw, and use those angles to display the crosshair. If the velocity vector has zero magnitude, you'll have to pick a direction arbitrarily (probably forward) or even better, not display the crosshair at all.
Your display code is ingenious, so I'd love to see a true vector indication using it. :)
I'm working on an horizon indicator, and I already have a bearing code on the workshop. Altitude is not accessable to programs and I doubt that I would be able to combine all those on one screen as making stuff with non-monospaced font is quite dificult.
Yes! The setup is EXACTLY the same as in the video, just for a large ship! The optimal text sizes should work too :)
@Zankar:
G-force has to do with acceleration. The position of the velocity indicator represents its relative velocity along that axis of travel. So if your indicator is halfway up the positive y-axis axis, that means that you are traveling 50 m/s up.
@LookAtMyHorse:
Thanks for the catch :)
And I'll see what I can do. Drawing is quite challenging with this system
@Uhthis:
Thanks, I wanted to make sure that I didn't break stuff on accident while coding. I guess it also helps users XD
would it be possible to make a mode with a straight line between the middle and the cross?
Thank you :)
I have better ways to spend my time.
I'm sorry, I can't read that language lol