This is a short example of moving platforms in Unity3D. Based on this tweet, I spent … 30 minutes? Maybe? putting it together. This writeup took longer. The approach uses two behaviour classes to achive the classical effect of moving platforms that follow some path. mark some empty GameObject as Waypoint instances give each Waypoint a next field attach a Mover instance to your platform(s) drag the platform towards the next Waypoint at a fixed rate when you’ve reached the Waypoint, continue with its next one My example;
I should just “blog” informally more often - so here goes. I’ve cobbled together a toolchain/asset-conditioning-pipeline of sorts for demoscene type stuff. My system is written in Scala on Gradle and functions by emitting C/++ and CMake files for Visual Studio. All of this produces a C/++11⁄14 and GLFW/GLAD/OpenGL4.3⁄4.5 executable that displays someone else’s ShaderToy project. Nothing revolutionary, but I’m after pretty-code that I can keep using rather than actual hard “street cred” quality demo results.
I wrote a threading primitive and I’m very pleased with it. I plan to wrap all of my “save file” things in this, from now on. Delay Run This class acts as a sort of “once inactive for X do Y” pattern. In my design, I’m wrapping my save actions in it and triggering schedule() after practically every edit. The class is passed a delay: Long value to specify how long to actually wait - I’m using 1.
Some clever clogs made a snazzy tool called SciLab as another not-MatLab.1 Flex Dock is the framework that (I think) they developed for docking frames. It’s not in Maven Central so I’ve forked it and deployed it to my own repository. convert the build The actual conversion was embarrassingly easy since the gradle importer stuff really works for this sort of thing. As a matter of personal preference, I re-arranged the build scripts to be a single file but otherwise left them as-is.
So … you’ve got a Pi3 running as a Docker host with some services that you want your buddies to have access to. You could try and get them to SSH into your home network; just like you could type all your programs with a touchscreen. I’m going to use nGinx to setup a reverse-proxy from my real-Pi3 to various Docker containers based on URL rewriting. I’m doing something else (of course) I’m setting up (what I call) name-based-virtual-hosting.
I’ve been assembling a “full stack”1 for development that runs on my Pi3. This is all happening inside of Docker containers which made cleanup redonkulously easy. Today I was looking at a source code management system; something of a “my own GitHub” which I can run on my own network. We have GitLab at work; so I wanted something different … also; the authors don’t suggest using a Pi3 for “real.
Login to your pi’s terminal, and run the following two commands. sudo su wpa_passphrase YOUR_SSID You’ll then be asked to enter the passphrase and confirm the passphrase. If they match; you’ll see a blurb that’s a config file fragment. Good. Now (still as su) repeat the last step, but pipe-append the output to the supplicant file. wpa_passphrase YOUR_SSID >> /etc/wpa_supplicant/wpa_supplicant.conf You won’t see the instructions this time - but that’s okay.
I had an idea/desire for a “simple” template class that’d work as my OpenGL thread. A contemporary design for multi-threaded 3D games10 seems to be pooling work and processing it in whatever threads are available. IME OpenGL/GLFW are not re-entrant; Apple2 and GLFW3 explicitly states that it won’t work - so it seems safe to assume that I shouldn’t call functions from different threads. So to make a super-fast 3D game (or whatever) I need to do less work on the thread which is running OpenGL while allowing other threads to send it whatever work they please.
This is a followup to a previous post because that one stopped working, now - this works. There’s not a lot of OC here, just clarity. NameCheap DynDNS on a Pi3 I use NameCheap (because they’re anti-SOPA) for DNS. The client program, ddclient, can connect to NameCheap. I’m using raspbian, so, first; run sudo apt-get install ddclient on your Pi find the dynamic DNS settings on NameCheap’s website Dashboard >>> Domain List >>> Manage >>> Advanced DNS they do like to change these things around halfway down the page, there should be a DYNAMIC DNS thingie enable it (if you haven’t already) note the blurb-what-looks-like-a-SHA edit your /etc/ddclient.
I connected my Windows desktop to our office file server using SSHFS rather than SaMBa. I am happy about that. For some reason one of our SaMBa systems got twitchy sometime last month. This is a problem since I’ve inherited a script that; I don’t yet understand runs on Windows (10?) exclusively reads data from \\foo\bar\project\user\project3\data\something paths Since I know that SSHFS already works, I’m setting that up as a substitue.