moggel

Is the ugly bitmapped window "reflections" some sort of placeholder in early access, to be fixed later on? They can be seen in daylight too (though much less pronounced) but starting a night mission and directing the flashlight out the window makes the problem very apparent: The interior is simply bitmapped onto the glass surface.

That was correct. I tried turning off the engine effect completely and that made me feel the G-force and other effects. I would've preferred having the engine effect on the ground and then, once airborn, have it dampened to a very subtle level and I did find that option and experimented with it. The problem is once I go below 12% for the engine effect it stops completely and starting at 12%, it gets very pronounced. I have the same problem with the G-effect: I set the dead zone to -1.0 <--> 2.5 but at 2.5G it's quite pronounced and there's not much difference as it rises to 6G so it's very much on/off. Is there something I can do to have it start softer and then gradually increase as I pull more Gs? If not it's not of much use as feedback I'm afraid.

Ordered a JetPad on Saturday and got it today. That was F-A-S-T (thanks @=Andre=)! However. I just wanted to try it out and I can't feel much of a difference. Tested with the Mustang and I'm very keen to check out the simulated G-effect feedback but can't feel anything special when I pull hard, fire the gun or land extra hard afterwards. The seat does start vibrating when I turn on the engine and there seems to be a difference depending on what I do with the throttle but that's about it. I tried increasing the G-effect in settings but that didn't do much. What am I missing? BTW the software crashed when I tried out the Mosquito, but maybe it needs to be updated for new aircraft models?

I saw the VR improvements Team Fusion is doing for IL-2 COD, and I'd love to see them in DCS, especially the rotation amplification as I'm a bit stiff to the neck these days and find it difficult to check my deep six without doing an hour of yoga every day. TL;DR; these are the improvements presented (that aren't supported by DCS): - Rotation amplification (like with TIR, you can adjust the progressive reaction of the view as you rotate your head) - Cockpit limiting your movement. No more sticking your head through the glass; makes for better immersion - Forced IDP Check it out:

Yeah, seems I need to keep cowl flaps open durin a perf-climb, contrary to checklist. I do go for 150mph with 9+ boost, as that is stated as max rate of climb (page 102). 175 is optimal for range, as I understand it (with 2650 rpm and 7+ boost. maybe I misinterpret the manual?

I must be doing something wrong here because I can't do performance climbs without killing an engine. I've been following the Climb Checklist for performance climb (+9 boost, 2850 rpm, cowl flaps closed, 150 mph) but so far I haven't managed to go higher than angels 13 before one of the engines quit. Oil temp is, at that point, somewhere between 60 and 70. I haven't found any advice on how to use the mixture in the manual so I left it at RICH. Any advice?

Thanks for the advice! I made some very basic training missions and took the 'stang up just to practice and see how she reacts at different altitudes while pulling different amounts of G. Seems I can sustain 2-2.5 Gs most of the time. More than that I need to dive and +4Gs can only be sustained a short while. An hour of practice wasgreat to train muscle memory and learn how to recognize when speed was starting to drop dangerously low. Now I can do turn fights and hold my own but it seems the AI wingmen will only engage for a few minutes, making the campaign missions very difficult. They usually end with me having to turn fight multiple bandits while the rest of my group just fly formation, mainly. Tried ordering them to engage or "cover me" but the bandits can basically B'n'Z me all they want, without any reaction from my AI wingmen.

Thanks for clearing everything out! I have ordered a JetPad SE from André. Really looking forward to add some extra immersion to the experience!

Been doing WWII campaign of late as I finally got a modern PC that can cope with 70+ bomber formation+2x12 fighter groups. The same pattern happens all the time: As my group spots the bandits I order Flight + 2nd element to engage (3rd element engages anyway it seems). They do engage for a few minutes and then rejoin, even though the place is still riddled with bandits. I keep telling them to re-engange. Some are "unable", others confirm but just stay in formation. It ends with me being attacked by multiple AI bandits, doing turn fighting with them while the group AI just keep flying formation. Is this a new bug or an ancient one ED hasn't come around to fix yet? Is there anything I might have missed and can do differently?

I'm currently playing through the Blue Nosed Bastards of Bodney campaign and I have no problem with any type of flying, landing, or bombing but whenever I get into a turn fight, especially with 109s, I keep tipping over and the Mustang tries to go into a spin. Might be I'm not gentle enough on the stick but I feel I have zero chance to stay in turns with anything. This happens at most altitudes. Some advice would be appreciated!

I'm looking to get one of those vibrating pads myself but I'm a wee bit confused as there seems to be (at least) two of them: Gametrix JetSeat, of various models (KW-901 & KW-908) and there's JetPad, which states it's "Powered by Gametrix). What's the difference and should I consider one over the other? Is JetPad some sort of "modded" JetSeat or how are those products related? If I get a JetPad; will it work out of the box or do I need some additional software, or hardware? Also, are there any real difference to the JetPad and the JetPad "Sim Edition", when used with a normal chair (not a sim rig)? Ping @=Andre=

Yup, that seems to do the trick. Thanks!

Got a new PC and tried reinstalling everything. - Set VoiceAttack up like recommended by VCP, including "Run as admin" - Ran Vaicom Pro installer - Restarted VA - Opened "Import profile" and browsed to specified folder: C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO RESULT: There is no "profiles" folder; not there or anywhere in the VoiceAttack folder tree What am I missing?

Yeah, I suspected that. I have been doing some mission building myself, for fun and to learn. Not nearly as advanced as your stuff, but even basic missions (without voice overs, additional graphics and loads of custom LUA scripting) is very time consuming, with tons of testing and balancing. Too bad but I can absolutely appreciate your policy.

@Reflected I just upgraded my PC from a potato machine (older i7, 16Gb RAM and 1070 TI) to a decently modern one (i9 11700K, 32Gb RAM and RTX 3080). I love your WWII campaigns but I couldn't run the Channel map at all on the old bucket - it was a slideshow. With a modern PC, however, I would absolutely buy all your Normandy-map based campaigns again if you made Channel editions! The Normandy map is "ok" for France but it's a bit of a shame not to be able to take off from Biggin Hill and to just sit there and try not to look down at the ugly, repetitive English landscape, while heading for the coast. I know you've made some bonus missions so far but would making Channel editions of the Normandy campaigns be interesting, or simply not worth it?

Finally upgraded to a decent PC. I moved the SSD with DCS World (beta) to the new box but I assume I need to reinstall the full deal? Can I just copy over the modules or do I need to delete them and install them from within the DCS modules UI?

Thanks. A. Lot! Really appreciate it!

I finally got a new PC so it’s time to start a complete re-install (I assume just moving the SSD from the old box to the new one won’t work?). But, obviously, I’d like to keep all my key bind configurations. Where are the files for that, so I can move them over to the new box?

Update: The reason I didn't get the COMMS menu was two fold: First off I had mistakenly bound a HOTAS button not to the PTT item in the configuration but to the line below it. Just a silly mistake. The other reason (when I corrected that) was that i was running VAICOM PRO at the same time (was trying to fix two problems), which is configured to suppress the COMMS menu. Duh! My remaining problem is that VAICOM does recognize what I am saying but the log says there's no recicpient. I interpret that as meaning I've pushed the wrong channel (in the P-51D). To get more control over testing I created a simple mission with just one wingman and made sure channel A is the one both me and my wingman is sharing. Still, I get this error. Any ideas what I might be missing?

Thank, I did that and it is the VR mike.

Haven't done all that much in VR yet so I thought I'd try a campaign. I picked the P51-D "Charnwood" campaign is I thought most other campaigns would be too much for my potato PC (my new one should arrive "soon" but until then ...). In the campaign I have not been able to use comms at all. VAICOM PRO doesn't pick up _any_ commands. I then tried without Voice Attack and just rely on the plain comms menu by pressing my binding to present the menu does nothing. Actually, very often as the mission starts, I get the comms menu to appear but only a few times. After that (usually after takeoff) pressing my HOTAS keybinding for comms menu yields no result whatsoever. I can still press WIN+R to have my flight attack the primary (a pain as I need to lift the headset to find the key combo) but no other comms option seems to be available to me. Am I missing something here or does stuff work differently when in VR? Or is it just my machine that can't cope?

I have now disabled Windows powering off my USB hubs in DM. Let's see if that helps.

I have sort of a potato PC (16Gb RAM) and, so, when I found a G2 I didn't really expect to be able to use it until my new PC arrives. To my surprise I've been having a pleasent experience both in DCS and MSFS2020. My settings aren't super high, og course, and I do get the occasional stutter but overall it's been working ok. One thing, though, is bugging me. Often when I play DCS the VR goes black. I can still see on the monitor and the headset is tracking fine but the VR "monitors" goes black and don't come back. I never see this behavior in MSFS2020, only in DCS (SteamVR). Anyone else seen this, or have any ideas what's going on?

Been seeing more than one gamer warning against replacing the Reverb headphones with a headset, as it can induce "severe claustrophobia". Sounds like that's not an issue for you at least?

Thanks! I will try that ASAP.