安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题






Means for as long as you attach this system to every vehicle you're playing with (keep active block presupposed), those vehicles will send around their data for as long as they have any battery left. And for as long as the vehicle you're using is in range it will be able to detect it.
I never got any feedback up to which amount of vehicles this system actually works, but from my own tests i can say that 5-6 vehicles are no problem at all, even on slower computers.
Honestly sounds like an understatement, losing boats or crashed helicopters seem to be an issue for me!
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2027281243
I am currently not working on it, cause the system seems to work so far and adding the missing parts would take some time which i currently don't have.
I admit that putting this together isn't really intuitive, that's why i decided to write a step by step manual for the Tracking System V2 which tells you exactly (hopefully) how to connect all microcontrollers.
I don't want to promise you too much, but i had an idea how i might be able to do that.
Might take a while. Hope it works.
Any plans of perhaps making the information about other ships show up on the map itself? That would obviously be incredibly cool. I'm thinking about making other ship icons clickable, opening up a new screen showing the info, with an arrow poiting to the left you can click on to go back to the map. The system itself seems to be functioning well enough that such a function is warranted in my opinion. However, I understand if you'd like to wait until are satisfied with your current project.
By the way, thanks for the compliments on my little edit on your map. I'll follow your suggestion and upload it. Thanks for letting me :)
As the LUA block, that creates the debug output, has enough space left, you could simply add a counter in the onDraw function, that counts to 120 or 180 before the text is drawn and then reset itself. So there only will be an output every 2 or 3 seconds, which will make it more readable. Might be okay for as long as there is only one other ship.
Otherwise you'd have to create a table and store the data in the onTick function and then cycle through it in the onDraw function, if you want to display data of multiple ships. Combined with a counter again, you might end up with something close to what you want.
But again, the debug output was never meant to really display data, it's only there to enable you to see if the system is getting any data at all.
The displaying part is the tracking system microcontroller.
How do I get the info if not through the debug? I can't see any feeds of information anywhere else :)
As this system was build to send data per tick and the debug channel outputs per tick, it is indeed very hard to spot any useful information. Especially if there is more than one ship sending.
To my defense, the debug channel was never meant to give you information about ships, it's just there to show you if there are any information at all.
Part1:
The composite output of the 9x5 (purple) goes into the the composite input of my zoomable map mircocontroller .
The video output of the zoomable map microcontroller goes into the input video input of my tracking system microcontroller .
The video output from the tracking system microcontroller goes into the video input of the 9x5.
And the composite output of this AIS microcontroller (called AIS Data) goes into the composite input of the tracking system microcontroller (also called AIS Data).
Part 2:
That's the whole system.
And the zoomable map is called zoomable map cause it has two touchscreen buttons integrated.
So you don't need any external buttons.
That also means, attaching two screens won't work, cause you can't attach both composite signals (touchscreen information of the monitor) to the microcontroller.
The second monitor will only show, but not work as a touchscreen.
Part 1:
First of all, thanks for asking.
There is a saying: you're only stupid if you don't ask.
Now about the connections.
The speed input comes from a Linear Speed Sensor, placed somewhere on your vehicle.
The signal strength input comes from the Radio RX Antenna (which every RX Antenna outputs, except from the small one).
But if i do remember it right, the signal strength input isn't used so far, so it might also work if you don't attach that.
And about the map zooming on a screen smaller than 9x5:
The whole system has been created for 9x5 only, i never had any smaller monitors in mind while developing it.
Means, if you want to get it running on smaller monitors, you'll have to edit the code and make it work for you.
Part 2:
I will add to the description, that you should see this system as unfinished,
The limitations in getting text from A to B via radio signal, plus the limitations you have in lua code size, actually broke my enthusiasm to make this like i once intended to.
So if you want something super high end, that works out of the box and in every situation, you might want to keep looking for other solutions in the workshop.
This system actually only shows you vehicles around you in different sizes and colors, depending on what values you've put in and also where they're heading.
Maybe someday i'll find a way and therefore the incentive to give this all the features an AIS System normally would have.
What should I insert in speed input and signal strength?
And how can you zoom a map on a screen smaller than 9x5
Yeah i'm a little stupid
if you meant something else, let me know.