Ourorborus

It seems to me that a very large portion of the bugs and complaints raised in these forums regard lighting. It also seems that whenever a patch fixes a lighting issue for some people, it simultaneously breaks the lighting for others. To bright for one user is not bright enough for another and so on. Common complaints include, cockpit backlighting to bright/dim MFD/DDI type displays too bright/dim. Cockpit interior (shadows) way too dark compared to outside. (particularly prevalent in the VR world) Player Aircraft external lighting too bright/dim AI aircraft (especially tankers) external lighting too bright/dim Ambient night lighting too bright dim. Often the cockpit adjustments are not functional or not linear meaning if they are too bright the lowest setting is still to bright. Without editing obscure lua files and applying trial and error to the results, the only brightness adjustment is the gamma setting. So, to account for the different hardware of users, I request an advanced lighting options page that would include sliders for: Cockpit shadows Cockpit/instrument backlighting External Lighting Ambient Lighting/gamma Or at the very least include these settings as options in a clearly defined "saved games" lua that does not break MP integrity.

+1 I have noticed an improvement on this front with the last stable update, I can sometimes see my cockpit instruments in the day now. The trade off was DDIs and cockpit lighting is now very dull. I fixed the DDIs by playing with the lua values.

This warning activates when you power up for take off if you haven't set trim with take off trim button. Press the button (or press the button then trim further for weight on carrier) should be part of pre take off checks. Sent from my F8331 using Tapatalk

Sorry didn't mean to hijack your thread. I am pretty sure my problem is well reported already. I can see a strange flicker effect in the shadow at the time you indicated. It may or may not be related to the existing longstanding shadow problems.

+1

I am not sure the problem lies in excessive fuel consumption. Formation aircraft generally burn more than lead in real life too. This is why fuel state reports are so important. Excessive use of afterburner is a problem as it should not be needed to keep station. What I see as the problem is that AI don't calculate BINGO correctly. BINGO is the minimum fuel state needed to RTB/divert/reach destination safely. Thus if the wingman calls BINGO, he is telling me we need to RTB/divert now to avoid running out of fuel. Many times have had my wingman call BINGO whilst RTB on best range profile and still eject prior to the airfield. This tells me the fault lies with the wingmans BINGO calculation, as he was clearly already below BINGO when we started to RTB, and was also clearly below BINGO when he called BINGO.

It works the same for me regardless of aircraft. (A10, F18, Spitfire, Huey). The Comms menu only appears when I say options, and that is good for me as I only want to see it when the voice recognition falls over and I need to select menu items. Why do you want to see the comms menu every time you speak? It sounds like you have some version of easy comms on (at least in the A10) as you are assuming the PTT will tune your radio. This is probably where part of your problem lies. Sorry I can't help you there as I have all radio helpers off. They just confuse a simple process in my mind. Comms in DCS is simplified enough without autotune etc. Just tune the radios in the cockpit and push the correct PTT. Most missions have the Studs (presets) defined in the brief/kneeboard, and if not manual tune mode can be used. Normally I tune COMM1 to flight internal (wingman) and COMM2 to ATC/AWACS/TANKER/JTAC as required.

I am just impressed by the fact you can see you cockpit in shadows at all! My cockpit is in perpetual night, and I need cockpit lighting all day. If I raise gamma to see the cockpit like your video the view outside is hopelessly washed out.

I'm not entirely sure what you are getting at here, but I'll do my best to help, forgive me if I am telling anyone to suck eggs. Firstly if you have VIACOM Pro. Map your PTT buttons in VIACOM. (most of us use the hat switch near the thumb on a warthog throttle) Then make sure those buttons are not mapped to anything in DCS. This is important as if you have the button mapped to radios in DCS and VIACOM the two will interfere with each other. Double check they aren't mapped in DCS Check under F18 sim, UI Layer and General. Now, In game you will execute most radio comms without needing the comms menu, just tune the radio to the correct freq on the UFC, press the appropriate PTT and speak. There will be some commands that do need the comms menu, usually when the speech engine doesn't recognise it (The MS Speech engine assumes everyone is American) or for mission specific options in the F10 menu. In this case simply hold PTT and say "OPTIONS" the comms menu will appear. Then say "TAKE X" where X is the Menu item number. So for F10 menu you would say, "OPTIONS, TAKE 10"

I use VIACOM pro, and have each radio mapped to the "comms hat" on my Warthog. It is free to try and I highly recommend it for VR.

Hollywood. Thansk so much! Will make the changes.

Thank you very very very much!! You sir are a gentleman.. No a legend.!:thumbup:

Are you cycling the bleed air knob during startup?

I have done the same. reverted to the last patch until this is fixed. Does anyone know how to disable the check for updates? Now I have a dialog telling me an update is available for VIACOM PRO every time I start Voice Attack. Not a biggy but it interrupts my DCS startup script.

I had plenty of difficulty in a10 and f18. The single best upgrade that helped was vr. Then formation practice. Set up a mission with another Hornet flying a huge triangle with long legs. Start the player acft next to it. Practice holding various positions in close form with that acft. And by hold I mean hold... A few minutes at a time. Then move to refuelling. Like everyone says.. Don't focus on the basket. Unfortunately, what they don't tell you are the visual cues to use. I know I will cop flack for suggesting this, but a tip for learning the correct cues is to simplify the task a little. As follows: Turn wake turb off. ( it is waaaayyyy over done anyway) this removes the sudden roll as you approach. Lock the tanker up so you see your distance and closing speed. Sit 0.1 behind the tanker straight and level and place the refuel pod (the big thing on the wing not the basket) on your 5degree pitch line. Use this position to match the tanker IAS. Now for the heresy.. hit BALT. This will do 2 things. It will dampen your inputs and will remove pitch (and associated speed changes) from the occasion. Now just creep forward 1-2 knots higher than the tanker until contact. Then concentrate on keeping the pod centred obove the HUD. Your cues may differ slightly but I find if I keep the pod between the top of the hud and the canopy frame I can fuel indefinitely. If the pod creeps up to the frame I need to back off the throttle a little. If the pod drops to the HUD I need to creep forward. I can already hear Spanish inquisition coming for suggesting the use of autopilot. However I am not suggesting you always use it, just use it to help learn the required visual cues and build the required reflexes to make fine adjustments. (although it's a game, knock yourself out if you want to) When you are comfortable with the visual cues, try without the AP. Remember your controls will be more sensitive when you do. When you are ready you can even turn the wake turbulence cyclones back on. On the topic of sticks. Find what works for you. Many here recommend super light sticks. I personally hate light sprung sticks and couldn't possibly fly well with them. The warthog is near perfect spring for me however I highly recommend having the stick between your legs. This let's you rest your forearm on your thigh allowing very precise movements. I personally place the warthog on my seat and sit with my thighs on the big plate. Very solid and comfy. Sent from my F8331 using Tapatalk

I would love to see civilian AI aircraft. I have no interest in flying civie acft in DCS. ( I have other sims for that) but it would be great to have civie AI aircraft along with Mode 3C transponders. This would force a bit more thought into Enemy assessments. At the moment, a lack of friendly mode 2 or 4 IFF is automatically classified as an enemy, and we shoot it down. In reality this could be a civilian aircraft......

No. I don't have the F14. Only VAICOM add on is the Supercarrier.

That's awesome. Well done

Downloaded and used this for the first time last night. Well Done Bankler! This mission is the best way to learn and practice case 1 landings. I don't anticipate I will ever get even close to a perfect score but the mission allows me to conduct many approaches in a short time. AND it helps isolate the points in the circuit where you are missing the mark. After one sitting I have already refined my Pitch/Break turn to to achieve a much more consistent downwind leg. Thanks!

Tried an Airstart and found take x not working, even as the first thing after loading the mission. Also tried keyboard shortcut also no joy. :( For me "take x" is completely broken.

I will try tonight or tomorrow after work. I will also look up what my keyboard ptt is (no idea if it is even mapped at the moment) and give that a go. :)

Thanks will do. There are various commands that seem to not like the Aussie accent. I'm not concerned as the VAICOM package is on the whole fantastic and I can live with the occasional use of "take x" to achieve the outcome. Provided "take x" works!

From many years as an ATC I always fly IFR turns at rate 1. This is 1min for 180deg or 2 min for 360 deg. I make my leg lengths standard 1 or 2 min until the final one. (1 min legs give a 4 min hold, 2 min legs give a 6 min hold) On my last hold. I establish outbound abeam the descent point. (i.e if I turn outbound at the descent point I will be on outbound leg abeam it). I then check the time. Calculate the time left to push time. Subtract 1 min and half it. That gives my leg length. very simple and quick to do. e.g. push time = 30; rollout at start of outbound leg at time 26:30; i.e. 3:30 until push - 1 min for the turn = 2:30 therefore each leg = 1:15 I will commence my inbound turn at time 27:45. Any wind effects are minor enough to adjusted by throttle on inbound leg.

+1 but please no American interpretation of the Aussie accent.(e.g. original point break closing scene) it is always so terrible.

Kaba. Hats off to you. This is a great campaign. A really good mix of tasking. And the storyline flows well mission to mission. Excellent tasking density as well. I. E not too simple. But also not over the top saturated. Currently on the low level trying to convince my stoopid wingman to actually follow the brief and hit the primary in one pass. Sent from my F8331 using Tapatalk