ruprecht

carrier ops wishlist Keep your pants on, I know that there's been no mention of this as a development priority, just thought it would be fun to brainstorm some features that would be desirable in DCS: Carrier Ops. Aircraft: I know loads of people are going to want the F/A-18E or SU-33, but finding data on them might be more difficult than with older aircraft. What about an A-6 Intruder? Carrier capable, ground attack role similar to the SU-25, might be easier to find data on it than some of the more modern aircraft? Carrier: It would be great IMHO to simulate the hustle and bustle of a flight deck, with realistic surface movement control, elevators, radio work etc. The boats in LOMAC are quite sterile in that regard (observation not criticism). It would be great for the carriers to come pre-equipped with themed scripts for flight ops, so that the mission builder sets a sliding scale for flight activity which is generated by the engine, rather than having to manually set up flights. So it could be anything from "quiet training day" where it's just you in the pattern, to "high alert" where there's a movement every 60 seconds and you have to slot into the traffic. Also an intelligent carrier would be great, responding to weather and wind by changing direction as required. Turbulence and "burbles" from the island would be interesting too. Radio work would be an important part of the sim, with approach calls, terminal guidance and a LSO calling you in on final and waving you off if necessary. Some sort of voice control integration would be superb here, if you could respond to paddles using voice commands? Hey, I can dream :) Anyway that's my thoughts. Interested to hear what others think. I for one would spend days just shooting circuits in all sorts of weather if the above ever came true! Never mind the mission aspects!

Yeap :) Haven't flown for real in over a decade though. Miss the flying, but not the military nonsense ;)

Peacetime only, so I'm not claiming to have any knowledge of combat statistics, but I would say that every 10th sortie there would be something noncritical in the maintenance book, or we'd get a chip light or something. This is based on OH-58, UH-1H, AS350BA and S-70A-9 which, in the former two's case, are admittedly old aircraft.

While I agree with every other thing you said, in my experience there is quite often something non-mission-critical that is U/S on military aircraft. Furthermore, helos aren't hospitable environments for anything that doesn't like constant vibration. In a warzone, where aircraft are being shot at and supply lines are stretched, I imagine that it's quite common to make a value judgement before you launch to accept faults with the aircraft. As I said, I agree that there are more important things to work on, but if any military helo went even a hundred flight hours without something lighting up or going U/S, the maintenance crews would be given medals.

Wow penguin, I'd love to have your coolness under fire! BOOM! The helo jerks left. "Right engine fir... BANG WHOOOOSH "Ruprecht has ejected". :)

I'm speechless with awe and admiration. I'm also looking at every panel I've ever made, and wondering if I should toss them out as they are testament to the hamfisted mess I make :)

Why do you fly on fully realistic, when there are helpful and colourful HUD radars and easy flight models and stuff available? :)

It does not. for reference, I'm running windowed 3x1280x768 on a TH2G, plus a 1024x768 ABRIS/Shkval, on a Q6600 OC to 3.2Ghz and 9800GTX+, 6GB ram on Win7_64. And I get acceptable frames. I'm not sure what hardware you have, but the new patch has helped a lot.

Curious as to who's using what sort of trim in DCS. I've reverted to the old 1.0.0 system.

With respect Obi, the OP doesn't seem to be referring to failures of the sort that occur in response to abuse (dust ingestion, icing etc) but more the "mean time between failure" type where something just quits for no reason. Like you're bumbling along and suddenly your ABRIS goes blank (and not from battle damage). I sort of agree with Rhino on these, but see that there's a place for noncritical MTBF failures. Essentially anything that completely cripples you (multiple engine failure, complete electrical failure etc) would end up getting restarted and that is more an annoyance than a challenge. But smaller MTBF failures, which challenge you rather than force a restart, would be welcome to me.

Crikey trigger, is that your A10 archive? there's some amazing stuff in there!

OK: - Autopilot issues were caused by the set of missions I was playing forcing easy mode. Back on hard, it all works as expected. - sound stutters still occur. Dxdiag attached. Downloading latest beta win7_64 drivers for my Asus Xonar DX PCIe soundcard, though not holding out much hope. Did anything change in the patch related to the sound architecture? DxDiag.txt

Ok will do, thanks man. Will check axis mappings etc, something may have gone squiffy with re-detection of my dozens of cockpit peripherals :)

Hi, I've recently patched to 1.0.1 and have noticed a couple of bizarre issues. 1) When I am lit up by ground fire, I get horrible graphical stuttering (about 1 FPS) and after my framerate returns to normal, I have usually lost some random sound channels, be they rotor sounds, voice warnings etc. It seems almost as if the sim runs out of sound channels and fails to free them up again properly. I never had this issue with 1.0.0, and I haven't changed anything other than installing the patch. 2) autohover, route mode and auto turn to target do not work. At all. The annunciator lamps come on, and e.g. for autohover the little square appears in my HUD, so the modes are definitely active, but it's as if the autopilot functions are totally missing. I was previously able to use all of these functions fine in 1.0.0, so it is not a knowledge or procedure issue, unless the procedure has changed in 1.0.1? All my AP channels are active, FD is off, I come to a stable hover and trim properly, engage autohover, the mode appears normally, but the AP makes no effort to keep me in position. None. Auto turn to target doesn't work at all. Route mode throws my nose all over the sky and makes no effort to fly the trimmed parameters. FYI I am using the LWin-Home startup procedure, and I have unticked the new trim system as I find it much harder to use than the old one.

Ah, good point. Pwned :)

I posted about this about three posts down :)

ED asked that multimon questions go in here: http://forums.eagle.ru/forumdisplay.php?f=96

I thought I'd start this thread to let ED know what we as cockpit builders would really like to see in their sims. Please try to keep it on topic and constructive, and please limit it to items specifically for cockpit builders. Other issues with the sim (trees, AI etc) have been done to death elsewhere. We are hoping that ED recognise that though pitbuilders are a minority group when compared to the wider user base, we are their most dedicated and passionate customers. My starting requests: - Discrete keymappings for every switch and knob position. Cockpit builders need one keymapping for Gear Up and one for Gear Down, not a single "toggle gear". Toggles lead directly to switch synchronisation problems. The rotary on the Targeting Mode Control panel is a classic example - only two commands, Rotate Left and Rotate Right - for a five-position switch. It doesn't matter if they're left unmapped by default, at least please give us the option to use discretes if we need to. - Every indicator state (lamps, text displays, lit pushbuttons, warning lights etc) available in Lua Export. - A10C MFDs available for separate display. I assume, given the excellent inclusion of Abris/Shkval export in BS, that these will be included in the initial release. Here's hoping that the Thrustmaster MFDs will include OLED/LCD displays and we'll have ready-made MFDs! - Easy switching of push for power and pull for power on HOTAS. Many of us elect to pull for power with the HOTAS throttle in BS, as this more closely replicates pulling on a collective. However on the A10's release, we will want to push for power again. If we have to go deep into the DCS controller options to do this every time we switch aircraft, it will get painful. Would it be simple to include a keymapping for "invert throttle" so that we can map it to a switch?

I won't know until I play with it, hoping to get one for father's day :)

http://www.vaaf.net/wiki2/index.php5?title=Black_Shark_MultiMonitors Note that after 1.0.1 you do not need to configure a phantom or run the phantom fix exe.

http://jaycar.com.au/productView.asp?ID=SP0753&CATID=28&form=CAT&SUBCATID=652 I've not been able to find a datasheet for them, and there's no identifying information on the switch other than the part number which doesn't really help on google. There are a number of options here too: http://au.farnell.com/jsp/search/results.jsp?N=1002101+500001&Ns=PRICE_PLS_018_PRICE1|0 If you're going to make panels yourself, the only power tools you need really are a drill and a jigsaw with metal and wood cutting blades. I'd recommend though that you get a cheap drill press, as they make drilling accurate holes much easier. Also check this book out.

Hiya, I make the panels myself. They are a 1.2mm aluminium plate for mounting the switches, then a 4mm masonite plate, to which is spray-glued a printed graphic, then a final coat of spray matte varnish to protect it. The switches are all store-bought. The ones used in the targeting mode control panel have a label insert made from inkjet-printed paper. The light shines through the white areas.

All multi-monitor stuff goes into game controllers now, I'm not exactly sure that it makes sense but there you go.

um... you mean the current patch isn't for the online english version?

You might want to try the LOMAC forum, not the Black Shark forum. http://forums.eagle.ru/forumdisplay.php?f=39 Cheers