epoch

Great! Will the fixes you listed in August but which still don't appear to be present in either build be included in the next update too?

It's fixed in neither (despite changelog claims to the contrary). Hoping for a fix soon. It's by no means the worst bug in the module, but it's near the top of the list for sure! But .. they're a real small team and presumably this is a hobby, not a full time job, so we've just gotta try to be patient and understanding.

Sorry this is OT, but what VR headset do you have? If it's Vive I'd love to know what settings you're using. I'm really struggling to read the cockpit labels. I've been through the threads in the VR forum several times but I can't seem to find a good configuration. (Vive + 1080 Ti).

Yeah 1.5.7 seems fine. To be fair, I didn't see the patches listed in the 2.1 changelog so that could explain it. Perhaps I misundertood Borchi's words (quoted below, underline is mine) and he means higher than 1.5.7 in just the beta branch, not alpha:

I'm thrilled for you! Enjoy! Unfortunately, I do. Fresh install too.

Any idea when these fixes will be applied to the Open Alpha build? (Sound bug, no tail etc still present in 2.1.1.9459.269). Thanks!

I don't think the fix is actually released yet. At least, I tested yesterday and nothing is changed yet. Still the bug.

I hope you can understand people's impatience and frustration, but for sure the upcoming patch will be very welcome and your hard work is much appreciated. Thank you. Do any of the fixes in the patch address the Viviane TV display 'stutter' when flying the Gazelle in multiplayer/2-crew? Or is that something ED need to look at?

That's a bit unfair on the OP given that there actually is no patch for the Gazelle today. The changes they announced will for sure be most welcome ... when they arrive.

Good news, thank you. What is this, and what issues does it resolve?

Paypal has buyer protection. Get in touch with them.

Yeah, it's very disappointing. Thankfully, even if ED aren't prepared to offer refunds then for those customers who wish to do so, if they paid using their credit cards they can request a chargeback from the card provider. I guess the card provider then recovers funds from ED ... who then recover from PolyChop. Certainly that's true for the UK and (I assume EU). I'd rather my hard-earned cash supports an active module developer.

Indeed. The fact this module still has so many issues, with no obvious signs of development, is worrying. The enjoyment factor is no longer there. A credit card chargeback is looking an attractive option right now. Early-access/alpha or not, one reasonably expects to see some development progress and not in-house drama. Such a shame. This module was so promising.

Did this work for you Dogman?

Hi Was this in the L variant? That doesn't have NVG enabled by default but you can do some simple tweaking to enable it. See my thread here from a few weeks ago when I had the very same problem. Should work on the Mistral too. The M certainly has NVG. Usually takes 2 or 3 seconds to come to life though. Hope that helps.

Hi My buddies and I have been enjoying various missions in the Gazelle (mostly self-made and also some we've modified, such as the A10 CSAR mission). Due to a Gazelle sound bug, if we get killed we need to leave and rejoin the server (otherwise we go mad). However, after doing this we notice that targets are out of sync between the player who joined-in-progress and players already on the server. For example, in the CSAR mission a convoy of APCs may be visible to players who didn't leave, and either invisible to me (rejoining) or in another place entirely. Is this a bug, or is something missing from the mission? Thanks in advance for advice.

Hope this gets fixed soon. It's frustrating in multiplayer having to leave and rejoin the server, only to then find targets out of sync with players who remained on the server.

Do give it a try. It's lots of fun. I think you mentioned earlier that multiplayer is something you're interested in, so you should be fine. There's some frustrating multiplayer bugs (sound & sync issues) but with any luck they'll be fixed once Polychop get going again. And it's still fun in MP despite the problems. Crewing up with a buddy is a blast. :joystick::fear: Enjoy!

Polychop have produced a product that's fun to fly and I look forward to future development of it. I also assume that creating the product isn't their primary job and that they all have real lives, jobs etc. So one can appreciate things taking longer to develop than we would ideally like (and for sure we're all keen!). That said, a less discourteous response from someone representing the developer would certainly be more palatable. As VampireNZ rightly alludes to, this isn't some mod team working on a free download for us all to enjoy. We paid. Nevertheless, really enjoying the Gazelle and look forward immensely to future development according to whatever timescales fit in with your priorities. Just perhaps be a bit more understanding that your customers are genuinely interested and excited to see development progress.

Apparently so but I'm struggling to get it working. In our test mission at the moment it seem to start auto spotting targets, each time incrementing the laser code by +1, but my A10 buddies aren't picking anything up on scan. Perhaps I'm misunderstanding the mod?

Did you work it out? I'd very much like to use this too. Any advice from you mission experts out there would be very much appreciated!

Yes it does! Thank you very much for your help!

Hi all I'm getting back into the A10 after a lengthy absence. I use Hawg Touch on my 2nd monitor to display and manipulate my MFCDs and UFC. All working fine. I'd like to get the CDU on the 2nd screen too, but I'm struggling with it. For sure I've done it before (quite some time ago) because my monitor setup file still has the relevant lines: _ = function(p) return p; end; name = _('MFCD+UFC'); Description = 'Camera on left screen, MFCDs & UFC on right screen' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 2010; y = 73; width = 403; height = 403; } RIGHT_MFCD = { x = 2628; y = 73; width = 403; height = 403; } [color="Red"][b]CDU = { x = 3238; y = 36; width = 226; height = 171; }[/b][/color] UIMainView = Viewports.Center The screen coordinates in the monitor file match the Hawg Touch panel's location. However, I can't remember how to get the CDU to display. I think it was something to do with the CDU_init.lua but having only recently re-installed DCS that file is stock, so I'm not sure what modifications I need to make (if any). Advice/guidance on getting this set up would be much appreciated. Thanks!

Yup, agreed. I just modified my graphics settings for when I'm flying the choppers (for which I primarily prefer to use the indicator). I don't use dual screen for those so I'll make do for now. Perhaps at some point Polychop will follow the .. I guess informal .. standards that all the other modules appear to follow.

Hi there There is no folder named ControlsIndicator for the Gazelle. I've checked on both the OpenBeta and OpenAlpha installs - nothing. I've added a directory listing of all files/directories in the spoiler tags below. The controls indicator does work in the Gazelle, so something's allowing it to appear. And like I said in my previous post if I manipulate the base.init_p setting in cockpit\Controls\base_page.lua it has an effect on the indicator (in that it fails to appear .. or perhaps appears somewhere I cannot see ..?). Thoroughly confused :unsure: Gazelle directory listing: