Goran_M Posted August 15, 2018 Author Report Posted August 15, 2018 (edited) Laying down carpet and rubber mats. Carpeted section in front of the Centre Pedestal hides the panel for the emergency gear extension handle. Clicking on that will move that panel off to the side. And the cockpit seats. Edited August 15, 2018 by Goran_M 9
ilias.tselios Posted August 22, 2018 Report Posted August 22, 2018 (edited) My english...dictionary is too poor to express my feelings...except drooling! (Where is the emoji for that ) Edited August 22, 2018 by airfighter 1
skiselkov Posted September 12, 2018 Report Posted September 12, 2018 So as you fine folks may already know, in our usual style of going completely overboard on the level of detail, a few weeks back I've implemented a custom VHF radio signal propagation model. This means, NAV radios (VOR, LOC, GS and DME) are all simulating things such as terrain masking, terrain diffraction, tropospheric scattering, etc. The underlying computational model is based on the NTIA Irregular Terrain Model (ITM), an industry-standard model used for things like radio tower planning. The simulation includes a built-in analytics display that allows you to check the terrain profile being used by the radio model (please note, the image below isn't hand-painted, it updates in real time as you fly): What's recently new is that I re-implemented the ADF and standalone DME radios as well. So the entire radio complement in the TBM is as follows: Two VOR/LOC/DME radio. One ADF radio One standalone DME radio That involved re-implementing all course deviation needles and the DME tuning pages on the PFD. All features of the real G1000 are simulated, even some of the more odd ones: ADF, ANT, ADF/BFO and ANT/BFO reception modes. This is reflected in the audio ID portion, including the continuous tone you hear in BFO mode when no ADF signal is being received. All DME tuning modes simulated, so NAV1 slaved, NAV2 slaved and HOLD. Allows for flying the more bizarre approaches, such as NDB/DME. Intercom audio routing from the radios is properly implemented, so NAV1 & NAV2 buttons route the audio ID for the NAV1/2 VOR/LOC portion, the DME button routes the standalone DME radio audio (including 1250 Hz square-wave tone, instead of 1kHz sine wave) and the ADF radio routes the ADF radio audio (including proper tone & background noise behavior depending on reception mode). 5
birdy.dma Posted September 12, 2018 Report Posted September 12, 2018 You are usually fantastic. Now you are incredible. I can't believe what i just read in your post. PS: have i any chance to write a smartcopilot.cfg file for this bird?
skiselkov Posted September 14, 2018 Report Posted September 14, 2018 On 9/12/2018 at 9:22 PM, birdy.dma said: PS: have i any chance to write a smartcopilot.cfg file for this bird? I'm happy to assist others in writing one, but I don't plan on doing it myself. While I would consider shared-cockpit a core feature requirement for an airliner, the TBM is almost never flown multi-crew, so that puts the feature rather low on the priority list from a realism perspective. And a second reason is that the airplane runs tons of randomizing code that gives it the "organic" feel of every flight being different, every system responding a little different to inputs, etc. Replicating that between two nodes would be a major undertaking and I'm not really sure is even practically possible (at least to my requirement of stability & usability) by using smartcopilot's simple dataref syncing approach. I suspect it would take a much more integrated approach that would talk to the internals of the systems simulation directly. 2
birdy.dma Posted September 15, 2018 Report Posted September 15, 2018 9 hours ago, skiselkov said: I'm happy to assist others in writing one, but I don't plan on doing it myself. While I would consider shared-cockpit a core feature requirement for an airliner, the TBM is almost never flown multi-crew, so that puts the feature rather low on the priority list from a realism perspective. And a second reason is that the airplane runs tons of randomizing code that gives it the "organic" feel of every flight being different, every system responding a little different to inputs, etc. Replicating that between two nodes would be a major undertaking and I'm not really sure is even practically possible (at least to my requirement of stability & usability) by using smartcopilot's simple dataref syncing approach. I suspect it would take a much more integrated approach that would talk to the internals of the systems simulation directly. Good day, Training is also the purpose of smartco. With newbies, I always start with the stock Cessna. Discovering and learning with a friend is always a pleasure. Anyway, smartco hate randomized code, so, it’s a no go. Don’t worry, I will be an early customer! Have a nice WE. Claude.
argonius Posted September 15, 2018 Report Posted September 15, 2018 This looks all really exciting..... But will this product run on all platforms X-Plane supports, thus including Linux?
skiselkov Posted September 15, 2018 Report Posted September 15, 2018 7 hours ago, argonius said: will this product run on all platforms X-Plane supports, thus including Linux? I develop on Linux, so yes, it will support Linux, Mac and Windows.
Jacoba Posted September 16, 2018 Report Posted September 16, 2018 (edited) This is for XPlane, right??? You guys aren't building an actual TBM... Its awesome!!! Edited September 16, 2018 by Jacoba
argonius Posted September 16, 2018 Report Posted September 16, 2018 8 hours ago, skiselkov said: I develop on Linux, so yes, it will support Linux, Mac and Windows. Good man! I am even more excited now!
Recommended Posts