Initial impressions:
The base is beautiful. Plenty of little things to do with it, too. Kudos!
Thanks for the positives!
The winged launchway has
very small clarances on the side when you're launching an XR5. I'd guess less than a meter or so. If any of the future XR vessels end up with a wider wingspan, they simply won't fit in the launchway. Ditto with the hangars.
The longer takeoff distance is a really nice touch, especially when you're launching an overloaded XR5.
WRT to clearances. Yes i am aware there are a few cloase calls and things are a little tight. This is the result of 2 things mainly. Firstly, Some of the original meshwork was done bloody ages ago, so was designed around the DG, not the XR2. I will increase clearances of the small lease hangars accordingly. As the the XR5... she's bloody huge! I decided on small clearances for her so that the hangars dwarfed every other vessel as little as possible, plus pilots like accuracy!
That said, I do appreciate things are tight on the Launchway particularly, I will take a look at this.
Landing Pads:
First, this is an absolutely beautiful idea.
As your later post pointed out, the correct rotations are there but, like you, I recently discovered it unfortunately makes no difference wrt to scn editor, which doesn't seem to pull that info from the cfg. I doubt there is anything to be done about this. All I can do in the meantime is to add the relevant rots to the manual, so people at least know what they should be.
Taxi Lights:
Again, wonderful idea. One suggestion for it, though - have them switch off
Aye, agree with face, good suggestion, it'll go in.
Tower MFD:
This is again a cool idea - would it be possible to have it in its own little window, though?
face has answered this in detail, explaining the rationale, so it is likely to stay as is I would think.
Also, I'm assuming certain functions (like getting the bearing to Wideawake) aren't functional yet. Otherwise, this is a bug. ^_^
Aye, as face says, it's WIP. The manual should state that, apologies if it does not.
Runways:
Is it possible to extend the ILS range for the runways?
Noted, this was an oversight, the ILS beacons on recently went back in, so I will increase this. 100km enough?
All this stuff being said, I love the base. It certainly feels more interactive and "alive" than the previous Wideawake. I'm looking forward to seeing how further development turns out. :thumbup:
Thank you for your time and feedback, much appreciated. I'm keen to see how it all turns out too!
Took me a while to find as well. It's inside the launch tunnel. When you retract the blast shield, you'll notice it's curved. You then open the tunnel door to "let the exhaust out". Next time you're in the launch tube look to the right, where the blast door is.
Yeah, cheers for this. It is worth noting that atm all the launch doors are manually controlled, this is WIP. When the Launch wizard is in, the doors will operate automatically depending on what pre-launch/launch request you make.
The amount of complaints is irrelevant to me, the quality of feedback is what matters
.
Indeed, you can't please everybody! But I have to say the level of feedback so far is very constructive and considered, so thank you all!
I'm not sure if capturing the keystrokes into an external dialogue without having the focus on it is even possible, of course - if it isn't, I agree with your assessment that it may end up being a clunkier interface than the MFD.
Face has done most of the talking on this issue, and I agree with his responses. I think the MFD route is the best one for orbiter, as it is the standard way to interact with things. Whilst the ATC will add another layer of feedback beyond the MFD per se, I do still believe it the best interactive tool to use.
The second issue is with the ordering of Ascension in the base list. This has been a problem I've noticed since the first time I downloaded Wideawake. The base is named "Wideawake International," but the config file is called "Ascension Ultra.cfg". Renaming the config file to "Wideawake.cfg" puts it in the proper alphabetical order in the list.
This is my doing. The base was titled "Ascension Ultra", but I changed it to "Wideawake Int" AU just before beta, withouyt telling face! I know this jumps it up the list and I will get this rectified. But it was a last minute change and I assume there will need to be a subsequent change in the loading code if we change the name of the base.cfg file, hence why I didn't do it before release. So we will get that straightened out.