This profile is a modification of Octavi's stock MSFS General Aviation GNS530/430 MobiFlight profile, adapted for the C172's dual Avidyne IFD550 (FMS1) / IFD540 (FMS2). It assumes you're already familiar with that base profile:
Everything not listed below is unchanged from stock (COM1/COM2, NAV1/NAV2, AP, and the FMS knob/CRSR/DCT/CLR/ENT/PROC buttons all behave exactly as documented for the GNS530).
an exploration of 3 conjectures in conversations with Claude.
| Conversation | Core Claim |
|---|---|
| I: Topology of Reasoning | The topology of a problem space determines the natural language for reasoning over it — and AI under RL pressure discovers this language |
| II: Mathematics as Structure-Adapted Languages | Mathematical specializations are such languages — and formal tools (category theory, Langlands, HoTT) can map their relationships and reveal undiscovered structural classes |
A practical guide to diagnosing and fixing crashes to desktop, stutters, and general performance problems in Microsoft Flight Simulator 2024. The techniques below are ordered from least to most disruptive.
Many third-party aircraft and systems in MSFS use WebAssembly (WASM) modules — compiled code that the sim runs for avionics, autopilots, and other logic. The sim caches the compiled output of these modules to speed up loading. When a sim update ships, that cached data can become stale or corrupted, causing stutters, display errors, WASM crashes (the "orange screen of death"), or CTDs — even with add-ons that were perfectly stable before the update.
We start out our MSFS 2024 flight in the LearJet 35a going from KFNT to KAMN. Since it's a short flight (47 nm) we'll cruise at 8000, averaging 200-250 knots.
View the spreadsheet calculations for this analysis.
First, we load the jet in FSE, 50% fuel, 467 gal.
| #!/bin/sh | |
| have_project=false | |
| implicit_project_file=false | |
| for arg in $@; do | |
| if [ $arg = "--project" ]; then | |
| have_project=true | |
| break | |
| fi | |
| done |
| # debugging helper for tracing variable changes across contexts in legacy code. The context information such as file, line, | |
| # class and method are automatically logged for you so you can focus on tracing the state mutations through various contexts | |
| # with ease. | |
| # @note this top-level method may be placed in config/initializers/lkdebug.rb and used anywhere | |
| # @note this method does nothing outside of Rails.env.development | |
| # @note legacy examples are intentionally bad code!! You should not write code like this, but if you have to debug code like this | |
| # you may want to dump state from various contexts within the program to understand what is going on. | |
| # | |
| # @param annotation [String] text comment providing context for the log. |
| require 'csv' | |
| class BooleanFunction | |
| attr_reader :inputs, :input_values, :output, :output_values | |
| BOOLEAN_SET = [true, false] | |
| def initialize( inputs:, output: nil ) | |
| raise ArgumentError, "inputs must be an Enumerable of symbols" if (!inputs.kind_of?(Enumerable) || !inputs.map{|e| e.is_a?(Symbol) }.reduce(:&)) | |
| @output = output |
| --- | |
| # defaults for all envs (local/deployed), (nonprod/prod) | |
| defaults: &defaults | |
| encoding: utf8 | |
| adapter: mysql2 | |
| read_timeout: 10 | |
| write_timeout: 10 | |
| connect_timeout: 10 | |
| reconnect: true |
| declare -a arr=("violin1" "violin2" "viola" "cello" "bass") | |
| for inst in "${arr[@]}" | |
| do | |
| #inst="violin2" | |
| title="Souza - The Stars and Stripes Forever" | |
| # create a blank letter page for titles |
