The ‘n’ node manager easily installs latest or stable versions of Node.js. Install with npm:
npm install -g n n stable
Done.
Comparing screenshots of Microsoft Flight Simulator 2002, 2004, FSX and 2020 (part 2)
Before the launch of Microsoft Flight Simulator 2020 last year I took a number of comparison screenshots in FS 2002, 2004, and FSX but I never went back and retook screenshots from FS2020 after the launch. Here’s one example of the level of photographic detail in the scenery compared to Visual Flight’s VFR photographic scenery add-on for FS 2002. It wouldn’t be a good comparison to the base products without a scenery add on since they were only doing scenery autogen and didn’t even have photographic scenery, but here’s a good comparison just how good the FS2020 scenery is (drag the bar to compare):
Since the recent UK scenery update, here’s a comparison in roughly the same area looking along the Southend coast. Unfortunately I didn’t have a screen from before the update showing where the pier should be – originally it was submerged in the imagery, but as you can see from the image on the right above it’s now a very impressively modeled landmark:
Here’s a couple of other screenshots taking a closer look at the scenery along the sea front and the pier:
It’s interesting while the pier got a full custom model, the fun fair areas each side got a couple of buildings but the rides and rollercoaster where just left as flat imagery:
Sending Packet Radio beacons with ax25 ‘beacon’
The ax25 app ‘beacon’ does what it says, it sends beacon packets, by default every 30 mins, e.g.
beacon -c KK6DCT-6 1 "Hello from KK6DCT-6 node!"
By default the callsign will be what you’ve configured for your node/tnc, but you can change that with the -c param. The next param is the ax25 interface number from /etc/ax25/axports, followed by your beacon message.
Working Packet Radio with a VT132 and a AEA PK-232
I’ve posted before about using a VT132 terminal board to control a PK-232 packet TNC. Here’s a few more specific steps and commands.
On first startup after doing the * auto-baud detection, the first thing you’ll see is the “cmd” prompt. If this is your first time setting up, or if the internal battery is low and it’s not preserving your settings since last time, the first thing you’ll want to do from the cmd: prompt is set your callsign (set your own callsign here):
my KK6DCT MYcall was PK232 MYcall now KK6DCT
If you’re working VHF packet, turn on VHF mode, with:
VHF ON
If it was off, now it’s on.
Set baud to 1200 for VHF packet:
HB 1200
Now enter D to disconnect, and we’re ready to send some packets. To re-enter this command mode, press Ctrl C.
By default the PK232 has a MPROTO value of OFF which doesn’t display any received packets other than those sent to your callsign. Set MPROTO ON and you’ll display other packets heard.
Additionally, the default value of MON as 4 will show some but not all packets. Set MON 6 to display all packets decoded. If you’re hearing other packets but they’re still not being decoded, enter WHYNOT ON to get an explanation.
At this point you’re ready to go. C NODENAME to connect to a nearby node!