#Traveller#2300AD Near Star List (expanded) in yellow, sky chart as viewed from Earth and cartesian map. Really an exercise to make sure my three-year-old code still works and to make sure that I still had the Gaia and expanded NSL available.
(edit:) as a side note, you can tell the NSL authors didn't really understand the DM or other star catalogue naming conventions, which usually follow xx(declination)(number) but you'll see catalogue stars with impossible declinations - those are invented
It is, of course, necessary to verify that any tool you build for #Traveller also work for the real world (if you're trying to keep Traveller at least vaguely hard sci-fi). So, in honor of the upcoming solar eclipse, here's my Traveller system simulation tool predicting the path of the total eclipse.
As an independent Digital Artist & Photographer, yes a sale is great, but it means more to me to offer you a browse, that’s why i also offer a Link to one of my galleries.
The automatic border finding and drawing needs considerable work and it doesn't look good yet. I want to do the equivalent of a morphological erode and then dilate to smooth it out, but there's probably a better method. Still whittling on it #traveller
#Traveller Imperial Bureau of Propaganda and Statistics report: Resurce Unit distribution through some of the Imperium: A green disk represents a world with a positive RU value, a red disk is negative, black points are 0 (for whatever reason). Through the travellermap data, RU is distributed approximately as a normal distribution with mu = 496, sigma=1906. The size of the disk represents how many standard deviations above the mean that particular world is, with red disks how many standard deviations below 0 the world is. Between 0 and 496 are all collectively treated as 0. Interestingly, the Solomani Sphere doesn't have all that much economic power, world by world.
The various maps of the #Traveller charted space borders are really not consistent drawing to drawing. The Rebellion maps are particularly hard to sort out (in terms of what the map coordinates of the borders are relative to the original map) because the borders are actually changing. But major features change position too.
1G Trader launch from Regina in #Traveller - the first 1000s. Even though Regina's surface gravity is significantly under 1G, it's enough that the 1G trader seems a bit sluggish getting off the ground. I'm presuming the spaceport is at -15, -60 (latitude, longitude) and the viewpoint is hovering over -40,-52, so the viewpoint is rotating with Regina in Regina's frame, but the path trails are in the non rotating cartesian frame.
#WIPSaturday#traveller - automatically (or at least, semiautomatically) generating maps of the Imperium from travellermap datasets, but trying to match the general style of the original Imperium maps
#Traveller outgoing ship at 1G then incoming ship at 1G. Lighting set from the direction of Lusor, it turns out that both launch and landing occur at night (which I hadn't checked before setting this up). (City lights are randomly placed, I'll have to actually plot out the cities)
#Traveller Trying another method of automatically drawing the Imperium borders. For this one I do a Region Union of each imperial hex, then a series of dilations and erosions to get rid of smaller islands and holes.
#Traveller automatic map generation: Now the borders for every alliance are determined, so long as the area controlled by the alliance is more than a few square parsec in size. All worlds from travellermap Milieu 1105 that are not Faraway or Unreviewed are included (about 68k worlds). Dots representing worlds are proportional in area to world GDP.
The assorted surrounding mini-empires and states adds to the feel (I think) of the original #traveller map - Now every Allegiance represented in the travellermap data is included.
#Traveller Trader detection of stern convergence intercept: A player without active sensors: that is to say, they don't know range or range-rate, but they do know the spherical position in the sky might have difficulty determining a firing solution or even determining if a pirate / customs boat (really all the same, isn't it?) were performing an interception. However, if you plot the object angular motion over time it becomes obvious that an interception is occurring. Here, for example, a pirate is doing a convergence intercept. Plotting the angular velocity of the pirate (blue) vs innocent outgoing trader (purple) and background celestial objects (Speck, Harcourt, and Assiniboia - this is in the Regina system as configured in Traveller5).
#Traveller#2300AD : A journey from Sol to Aurore (Eta Bootis). Of course no 2300AD ship can make the journey in one direct hop, but this is how the sky chart changes during the travel from Sol to Eta Bootis (home of probably the most famous world of 2300AD, Aurore). I plot any star with an apparent magnitude of 6, and only plot names of stars in the 2300 NSL, but I also plot the bright constellation stars so there's a sense of how the familiar constellations warp during the journey. Orion, for example, remains recognizable but it does change.
@sudnadja This makes me realize that a pure ASCII first person space game similar to Elite could be done ... no need for fancy graphics just the names with a "distance dot" underneath.
The " distance dot" is a digit from 0 to 9 telling distance magnitude.
@isaackuo I’ve done it in pure text with no graphics for traveller-like space combat, where the players are not given a geometric representation of the combat environment, just a list of contact spherical coordinates - and they didn’t even get the radial distance unless they were willing to radar or lidar ping the contact and then only if within sensor range (typically 1 light second). Distance had to be inferred by the angular velocity of the contact and possibly by apparent visual magnitude, which they sometimes had. It was kind of fun.
#Traveller 1G Trader landing on Regina: Guidance computer control inputs to engine during terminal phase (arrows represent direction of desired thrust). The guidance computer is a discrete time controller and updates guidance every 1/10th second. Touchdown velocity < 1 m/s.
@Hcobb It depends on the density and extent of the atmosphere and the shape of the vehicle. I typically do not simulate anything other than atmospheric drag as running full CFD can be quite slow. The code I'm using now I originally did for back-computing a meteor's orbit from observed flight through Earth's atmosphere, and in the meteor case it doesn't really change things all that much (I was within the range of computed Chelyabinsk impactor orbits from published papers with atmosphere both turned on and off).
