aboutsummaryrefslogtreecommitdiff
path: root/assets/blender/subway-train.blend
diff options
context:
space:
mode:
authorgpcf <gpcf@gpcf.eu>2024-08-08 23:53:29 +0200
committergpcf <gpcf@gpcf.eu>2024-08-08 23:53:29 +0200
commit45e5ad3b378b17be7e0ce314ba964e01792d673d (patch)
tree20802157fc7c0cbbbad9086fa3852971986c8ecc /assets/blender/subway-train.blend
parent3526fc2e4afbc0b33269d061ff676dd8613f11a8 (diff)
downloadadvtrains-45e5ad3b378b17be7e0ce314ba964e01792d673d.tar.gz
advtrains-45e5ad3b378b17be7e0ce314ba964e01792d673d.tar.bz2
advtrains-45e5ad3b378b17be7e0ce314ba964e01792d673d.zip
Fix boardcom train id display, add command to teleport to train by id
Diffstat (limited to 'assets/blender/subway-train.blend')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-03 05:30:18 +0000
78871bac3b'>Fix AIX threading buildShadowNinja2017-01-28 | * Fix synchronization issue at thread startShadowNinja2017-01-28 | | | | | | | | | | | | | | | | If a newly spawned thread called getThreadId or getThreadHandle before the spawning thread finished saving the thread handle, then the handle/id would be used uninitialized. This would cause the threading tests to fail since isCurrentThread would return false, and if Minetest is built with C++11 support the std::thread object pointer would be dereferenced while ininitialized, causing a segmentation fault. This fixes the issue by using a mutex to force the spawned thread to wait for the spawning thread to finish initializing the thread object. An alternative way to handle this would be to also set the thread handle/id in the started thread but this wouldn't work for C++11 builds because there's no way to get the partially constructed object. * Fix C++11 Windows build of threading codesfan52016-10-06 | | | | | | | The initial problem was that mutex_auto_lock.h tries to use std::unique_lock<std::mutex> despite mutex.h not using C++11's std::mutex on Windows. The problem here is the mismatch between C++11 usage conditions of the two headers. This commit moves the decision logic to threads.h and makes sure mutex.h, mutex_auto_lock.h and event.h all use the same features. * Fix & make linux conditionals uniform (#4278)Rogier-52016-07-04 | | | | | | | | The source used a hodge-podge of different combinations of different macros to check for linux: 'linux', '__linux', '__linux__'. As '__linux__' is standard (Posix), and the others are not, the source now uniformly uses __linux__. If either linux or __linux are defined, it is made sure that __linux__ is defined as well. * Fix Windows buildCraig Robbins2016-05-02 | | | | | Fixes the issue introduced by c1a0ebb (Fix use of uninitialised variable in class Event) causing Windows builds to fail * Fix use of uninitialised variable in class EventCraig Robbins2016-05-01 | * Fix POSIX C++11 buildShadowNinja2016-04-30 | | | | I broke this in 46fd114e9a4e05b74576dce682e24357363298e7. * Fix prepreprocessor error in thread.h (related to C++11 threads)Craig Robbins2016-04-30 | * Fix race on thread creationShadowNinja2016-04-28 | | | | This often broke the threading tests on OSX. * Fix C++11 compilabilityest312016-01-23 | | | | Previous commits broke it... :( * Fix events on WindowsBlockMen2015-12-11 | * Fix Event implementationShadowNinja2015-12-07 | | | | | | On non-windows platforms this just used a semaphore, which meant that multiple calls to signal() would result in wait() returning multiple times. * Fix misc. MinGW and Valgrind warningskwolekr2015-11-08 | * Time: use locks againest312015-11-04 | | | | | | | | | | | | | | | The Atomic implementation was only partially correct, and was very complex. Use locks for sake of simplicity, following KISS principle. Only remaining atomic operation use is time of day speed, because that really is only read + written. Also fixes a bug with m_time_conversion_skew only being decremented, never incremented (Regresion from previous commit). atomic.h changes: * Add GenericAtomic<T> class for non-integral types like floats. * Remove some last remainders from atomic.h of the volatile use. * Atomic: cleanup and add more operationsest312015-11-03 | | | | | | | | | | | | | | | | | | | | | | | | | Cleanup: * Remove volatile keyword, it is of no use at all. [1] * Remove the enable_if stuff. It had no use either. The most likely explanation why the enable_if stuff was there is that it was used as something like a STATIC_ASSERT to verify that sizeof(T) is not larger than sizeof(void *). This check however is not just misplaced in a place where we already use a lock, it isn't needed at all, as gcc will just generate a call to to the runtime if it compiles for platforms that don't support atomic instructions. The runtime will then most likely use locks. Code style fixes: * Prefix name of the mutex * Line everything up nicely, where it makes things look nice * Filling \ continuations with spaces is code style rule Added operations on the atomic var: * Compare and swap * Swap The second point of the cleanup also fixes the Android build of the next commit. [1]: http://stackoverflow.com/q/2484980