This weekend I spent a bit of time tidying (read: chucking out) in the ManCave in preparation for shifting things around. After a bit of organizing, sorting, moving, stacking and generally making a huge mess, I was able to turn the Skyhawk sim around 90º and into it’s new location. Then, after much cable tidying (read: chucking out) I moved my 2 primary PC’s into their temporary home next to the desk, and re-cabled everything again. I am **really** thrilled with how it has worked out so far, in fact there is a lot more space than I was anticipating. from my CAD modelling I expected it to be much tighter than it actually is…
Next step is to get rid of the un-used PC’s on the right, find a home for the printer so I can get rid of the cabinet it’s sitting on, sort out the cabling **properly** and find another piece of carpet to fill in the gap. I have/had plans for lifting the sim up maybe 300-400mm to allow for storage (and PC’s below the floor, but with more space than I thought in the room, I may not need to go down that track.
Tonight was going to be my ‘Back in the Saddle’ flight in DCS:World, after a lengthy absence. The launch, in a Harrier went well, dropping 2 Mk82 low-drag bombs accurately onto an enemy frigate, delivering the coup de grâce after my fellow aviators had damaged it earlier in the day. And that is where it all turned to rubbish….
The gimbal on my Thrustmaster Cougar has given up, and after some research it appears to be a not ‘uncommon’ problem. I’ve looked into options to repair or replace the broken part, and will probably end up machining a new part. A lot will depend on what I end up doing with my plans for the Skyhawk sim. One of the options I am thinking about is retro-fitting the Cougar to the Skyhawk, with a modified gimbal mechanism. The sim is potentially going to have a multi-purpose VR makeover….
Another evening of ‘doing stuff in the garage’ tonight meant some more work on the 737 Linings.
I’ve put enough fasteners in to hold it all in place so that I can plan the structure to hold it up. As I’ve said before; I want the sim to be fairly modular, so that I *could* move it in pieces, but mostly so that I can remove parts of the sim to work on outside of the confines of the enclosure it will be built into.
As part of the development of the 737, there will be a big renovation of the ManCave. For a start the 737 sim will be coming downstairs from the loft. The main reasons are access and temperature; not only is it hard work getting to the sim, it’s also too cold in winter, and way too hot in summer. The 737 will be just outside the current ManCave door, and mounted on casters so that it can be moved around to be worked on. The rest of the ManCave will have a shuffle with the TA-4 being turned 90 degrees, and going purely VR, while the ‘Instructor Desk’ will become more of a general purpose desk and be moved against the wall.
You can see in the render that it is a very cozy space, but with some careful and creative design I think I can make it all work and make far better use of the space than I do currently.
With the move downstairs of the 737 sim, I hope to turn the loft back into a useful storage space again, and recoup more space in the garage than the 737 sim will take up.
I received an interesting link via Facebook, to a database of US Air Losses during the Vietnam conflict. I am a fan of the F-4 Phantom, and of course the A-4 Skyhawk, both of which featured prominently during the era. The search function on the database was pretty cool, and after couple of sample searches, I entered my date of birth as the criteria, to see what, if any, aircraft were lost on that day.
Much to my surprise there was only the one loss, but it was a TA-4 Skyhawk, with the Tactical Callsign “PLAYBOY 45” and it was flying perhaps my favourite mission; Forward Air Control. Why it’s spooky; – The Skyhawk link is obvious, but even more so given that it is a TA-4, similar to my sim… – The callsign “PLAYBOY 45”; “45” was my pilot number, which formed the basis of all my callsigns during my time with RAAFvirtual. – The mission; FAC, my favourite, and one I’ve been working on lately in DCS!
It has been a while (seems to be a common theme) since I did anything on the Skyhawk sim… tonight, with a few wee software updates and other fiddling around I got the sim up and running, in DCS with the VSN Hornet. This was to prove that I could get the sim running using my combination of software and ‘mods’
This is the VSN Hornet, running in the sim, with Maverick TV feed working 🙂
After a bit of a revelation it occurred to me that for a very long time I have been trying to create a simulation environment in my sims which is almost exactly the same as DCS:World provides. I have been, for a long time, been trying to develop a multi-platform ‘combat’ simulation, using the tools with which I am very familiar. I found it very interesting that I opted to stay with my known and familiar environment, rather than taking a leap…. In this case I was very ingrained in the development of FS9 content, I was comfortable working in the environment, I could ‘talk’ to the simulation, I understood the way most things worked inside the sim. What I was really after was a complete combat simulation covering air land and sea warfare, with a Tactical Commander function. DCS:World has always been on my radar, I have ‘played’ around with it over the years, but never anything more than that. Recently though, with my interest in VR, I have been learning more and more about how DCS works, and how I can develop content for it, and make it into the sim I’ve always been looking for!
So. I am now ‘officially’ (as officially as I do…) I have stopped development of TACOPS and pretty much all of my projects around trying to morph FS9 into a combat sim….. My focus now is on development of content for DCS, focusing on NZ and the Cold War era. My 737 and Arrow sims will continue, running FS9 and FSX respectively, but wont be trying to be involved in any ‘combat’ mission.
It is very odd to look back and contemplate all the time and effort I have spent on a project which was merely trying to replicate something which was already around..
So now it’s onward and upward… I can concentrate on using the best software for each of my sims, rather than trying to make the one platform do everything I wanted.
SO, New software plan – TA-4k Skyhawk will be running DCS:World. – Piper Arrow will be running FS9 and/or FSX – Boeing 737 will remain on FS9
The deadline for having the sim at least “flyable’ was Saturday, and I made it… just. We had a group of friends over for a ‘BBQ and Sim’ evening, and my mission was to get the Skyhawk sim converted over to DCS ‘enough’ for them to have a fly around. This got further complicated when I discovered that my oldest controller in the sim was not Win64 compatible… which lead to some hectic re-wiring, and trying to figure out how I had wired some of the earliest panels from *many* years ago.
After a few beverages, and some good music I had it all re-wired, and ready to test. Only thing which didn’t work (that I’ve found so far!) was the gear lever, which wasn’t bad given the significantly compressed time-frame on this part of the conversion. With the hardware (mostly) working it was time to start ‘mapping’ the various buttons and switches in DCS. For the purposes of the Saturday night flying, I only mapped the more important controls, allowing all the novice flyers to have some nice scenic flying.
Before the flying night I had three eight year old’s test the sim, headed by Nathan, my Chief Test Pilot… I figured if some 8 year old’s had fun, then a bunch of middle-aged, half drunk motorcyclists would be fine 😉
I didn’t take any photos on the night, but everyone had a ball, lots of sight-seeing around Vegas, and some ‘unplanned landings’….
Next morning, slightly hung-over, I tidied up the display-extraction tools to correctly display the Maverick TV Images on the RH DU, then did a wee test flight ironing out issues with the weapons systems.
After the past weeks experiments and steep learning curve, I am petty happy with where the sim is at. The path to a more-functional ‘Kahu-esq’ Skyhawk is clearer than it was. I am going to try and merge some of the Community A-4E project, with a TA-4k visual model and A-10A avionics. This will allow me to shoot Mavericks, drop laser guide bombs, and fire Sidewinders. The only thing missing is a radar, but for the most part I think it will give the best compromise feeling.
Sunday night, sitting on the couch writing this, I feel that I have accomplished a lot in the last few days. There is a lot more to do, and a lot more to learn, but it’s a good start. A very good start!
Sometimes you just have to take the plunge, and last night was *THAT* time. After procrastinating for so long about changing over the main PC in the Skyhawk sim, I decided to just do it, and figure it all out as I went along. First step was to fire up the sim in it’s current state, to say farewell.. I was going to go for a fly, but with my motivation levels at a high point, and not wanting to get distracted I decided to just take a couple of final photos then rip into it.
The PC swap-out wasn’t too big of a deal, but running and sorting cables was… One day I will just rip all of this mess out and start again with cut-to-length cabling..
With the PC in place it was a case of figuring out what needed to be re-connected, and what wouldn’t work. So far the list of ‘wont work’ things is short; can’t connect my MIP monitor, due to the new PC only having one analogue output, and can’t connect my **seriously* old DB9 COM cable… which runs ACCIS. SO, PC in, fired up, windows updates done.. time to fire up DCS and see what happens. Of course, DCS needed updates.. many many updates, like 5Gb’s worth.
But finally, we got there! Nothing mapped, and only the stick <sort of> working but it flew.. and looks awesome!
Tonight I hope to start mapping some of the cockpit switches, and maybe define what I want to be able to do in the sim, at least in the short term.
After making my mock-up compass and clock I started looking for real components to replace them. It all started when I stumbled over an inoperative clock on a suppliers website, then a black compass showed up at work…. 2+2 in this case equals ‘yeehaa’ 🙂
After recently deciding on the software for each of my sims, and the shift of VR into the Skyhawk, I have had a bit of a re-think! This has mostly come about by my breaking out my old Thrustmaster Cougar HOTAS, and setting it up in DCS and FSX.
Another part of the reason for the shift has been a re-discovery of the joys of VR in other simulations. I spent a very relaxing evening driving from Oxnard, CA to Yuma, AZ in American Truck Simulator, which reminded me how much fun VR can be, beyond the ‘cockpit’ of the Skyhawk.
The new plan (until I change it again of course) is to run both DCS and FS9 on the Skyhawk, but skip the VR part, at least for now. I hope to put together a version of the A-4, with a modified version of the F-15C avionics, and simplified weapons, which will let me fly a ‘pseudo Kahu’ in the ‘pit, and join in multiplayer missions, while retaining VR capability on the current desk-based rig. This shift will mean FS9 will remain as the primary sim for the Skyhawk, with DCS being a development as time goes on.