Differences

This shows you the differences between two versions of the page.

--- events:conf:2022-06-25 [2022-06-30 18:35] – [Chat Log] I feel a bit guilty making it all about "me" 56independent
+++ events:conf:2022-06-25 [2023-01-12 22:19] (current) – [Graffiti on Wagons] Remove erronious double dot 56independent
@@ Line 26: / Line 26: @@
   * It was agreed a train painter track was a lower priority than the hand-based painter and should come later
   * The concern about survival mode was raised. There was a proposal that the wagon mod itself should handle coming up with the recipes and requiring materials.
-  * Later in the conference, 56i brought up the idea of making livery customisation available from the driver's seat. This was inspired by plane simulators where planes can be customised on the tarmac before taking off.
+  * Later in the conference, 56i brought up the idea of making livery customisation available from the driver's seat. This was inspired by plane simulators where planes can be customised on the ground before taking off.
     * Maverick2797 and others disagreed mostly because livery is irrelevant to the operation.
@@ Line 48: / Line 48: @@
   * Marnack noted that the DlxTrains implementation is to have the aging elements in the same texture file as the rest of the wagon, and use spritesheeting/cropping to select different aging patterns.
   * It was a agreed aging must be wagon-specific, because of the various sizes and UV map patterns of every different wagon. A generic 'paint chip' or 'rust spot' or 'dirt layer' probably would not work very well.
-  * 56independent mentioned that the train should be washable.
+  * 56independent mentioned that the train should be [[https://twitter.com/Thisiswow_/status/1544270426561724416|washable]].
     * I (Blockhead) think that like a lot of tools there should be a train washing hand tool and a fixed position train washer 'track' or larger apparatus.
     * There may also be a tool to artificially age wagons.
@@ Line 70: / Line 70: @@
     * The most likely requirement was train_operator plus wagon ownership; or wagon whitelisting to paint others' wagons; or train_admin to paint any wagon at all.
     * On some servers graffiti might not require any privileges.
-  * There was light-hearted discussion about whether advtrains would work on an Anarchy and/or free-for-all server, and about graffiti-ing public transport trains on servers..
+  * There was light-hearted discussion about whether advtrains would work on an Anarchy and/or free-for-all server, and about graffiti-ing public transport trains on servers.
 The conference topics had mostly been discussed at this point; the following topics are less related to livery.
@@ Line 98: / Line 98: @@
     * Doxydoxy mentioned that busted was good enough for his minitram mod with minimal use of the Minetest APIs.
+(Notes by @ywang)
+//The notes here are mostly to complement Blockhead's notes and to present my own perspective/thought when I mentioned these points during the conference. -ywang//
+  * @doxydoxy's destination display would also be useful for interior displays. (Later thought: I am no longer sure about this, considering that interior displays can have way more complicated styles than exterior displays. Some testing would be needed for this)
+  * With the eye attachment offset, it could be more sensible to attach the display on the train itself instead of using a HUD, and it could be possible to create a slightly more interactive control system instead of relying too much on formspecs. However, the MT engine has some restrictions for this idea (see Blockhead's notes). I considered this and the point above to be partly relevant to liveries as these are all internally implemented with textures in some way.
+  * The CI setup for the test world broke in mid-June due to an commit to MTG that required a later version of the MT engine.
+    * Note from later: For some reason I did not think about devtest when creating the test world. This turned out to be quite a mistake.
+  * As I was working on distant signaling around the time, I noted that some tests I wrote are not //strictly// unittests because there are tests that can be used for multiple components at the same time and creating individual tests would be relatively time-consuming.
+  * I also mentioned localization as it appeared to me that there was some interest in l10n. This point more or less boiled down to "take time for it - localization is not easy".
 =====Chat Log=====
 This chat log of the text was provided by 56independent.