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
2. I've had this happen before. You can rotate your model 180 degrees to be upside down in the scene and create the prefab again. I'm not sure why this happens but I think it's the module model or somehow setting your own module upside down.
3. Yes, add the highlightable as a child of the module part that you want highlighted. Also, check that it's not set inside the model or the highlight is put inside. You can also test the highlighting with the test harness for faster testing.
From the discord chat they said I only need to include the prefab inside the assetbundle so I removed all other things and it still looks the same.
I managed to make highlighting works, but what is "test harness" I can't find that.
I've rotated the module 180 degrees and the module is now upside down in scene, but it still upside down in the game.
BTW, I'm currently looking into how deserialize works on getting widgets status. Maybe you can guide me a bit on how dictionary thing works. :)
Thanks.
Take a look at example module 2 for querying the widgets. It shows the keys to use to get the status and how to retrieve the battery count from the response.