Hunter_5E

Try putting those files into C:\Users\YourName\Saved Games\DCS\Config\View and editing them in there. Works for me from there.

Posting this for all the people who would like to have Hellfires on the Shark or carry 24 Vikhrs or a mixture of Hellfires and Vikhrs but don't know how to do it. Very simple to do but nobody has posted this, so thought I would. For the purists out there... I know you say this is fantasy and ruins the game but I'm sure a lot of people will appreciate this and have fun with it. I'm certainly having fun with it and that's the main goal of any recreational activity - to have fun. If you don't like it, don't use it. Simple as that. Flying a Ka-50 is pure fantasy for all of us anyway. You'd never fly one in real life, so what's the problem in having fun with a mod? Live a little :) The only slight flaw with this mod is that Vikhrs on the inner pylons launch slightly upwards and not level like the outer pylons. Means they dip back down a fair bit to acquire and ride the laser beam, so you'll need to be at 10 metres or above so they don't plough into the ground. Hellfires work fine from all four pylons and are semi fire and forget. Wait for the Hellfire to finish its short climb and level out en route to target then switch off your laser. Move target box to next victim, switch laser back on again then lock and lase. Fire second missile. First missile will continue to last known laser location and second will track to new laser location. Rinse and repeat as required. Only works if vehicles are stationary though. Max range for the Hellfires is 7.8 km. Recommend 7.7 to be sure of a hit. (Your range will say 7.8 km but you might actually be 7.89 km away. Max range is aprox 7.81 Km so bear that in mind.) If you're going to mix Vikhrs and Hellfires, put the Hellfires on the inner pylons to avoid the dipping Vikhr problem. OVGME mod below. If you want to install manually, just copy the one file (Ka-50.lua) in the mod folders to here in your main DCS folder - \DCS World\Scripts\Database\Helicopters. Remember to backup your original Ka-50.lua file first. I run this in 2.5.6 stable. Haven't tested it in open beta Ka50 Hellfires and Extra Vikhrs.rar

No worries. Would have been nice but I'm sure I can live without it. Cheers.

https://www.digitalcombatsimulator.com/en/files/3308112/ Uses the Ka50 bin file as a base for the mod. Looks and flies like an apache but cockpit is still the Ka50 cockpit and hellfires are laser guided only so no fire and forget. Still good fun though.

Any chance you might be updating this mod? Still works and is good fun but breaks a bunch of stuff.

@russiandivxclub Make sure you're looking at control bindings for "Ka50 Sim" and not "Ka50 Game". The "L140 Laser warning system reset button" does not appear under "Ka50 Game" bindings.

Had a look at the iiyama site and they don't seem to offer much help on this issue. Found this with a Google search. It's for HP products but should be same troubleshooting process. Worth a look maybe. Hope it helps. https://support.hp.com/gb-en/document/c03488148#:~:text=Your%20touch%20screen%20might%20not,reinstall%20the%20touch%20screen%20driver.&text=Right%2Dclick%20the%20touch%20screen%20device%2C%20and%20then%20click%20Uninstall,reinstall%20the%20touch%20screen%20driver. Edit: I'd say yes, it is worth persevering with Helios as it does work very well with a touch screen. Certain aspects can be a bit finicky and frustrating but on the whole it works very well and adds a lot of immersion to the sim.

Update for Helios 1.4.2020.0530 and DCS 2.5.6 (I run stable, not beta) Fixed VHF2 radio frequency display - as detailed on Capt Zeen's Discord KA50 channel Changed PVI800 digit display to be handled by Helios, as exporting to viewport no longer seems to work with DCS 2.5.6 KA-50 Carbon Fibre 3 July 2020.rar

Never mind. Found a solution.

Can anyone confirm or dispel this? Can you successfully export PVI800 digits display or not?

Now that you mention it, I see this happens also in 2.5.6 stable.

Anyone else found PVI800 digits display not exporting since 2.5.6 stable came out? My export worked fine in 2.5.5 stable using the output name "MFCD_03 =". Any chance it's been renamed with the update? Can't figure out why else it would stop working as everything is ok in my monitor config file. Thanks in advance for any help you can offer. Cheers.

The reason I use bezel correction is because my bezels are big and ugly, 90 pixels each. At the time when I bought my kit there were no slim bezel LED TV's on the market so had to go with what I could get and afford (3 x Samsung 40"). With such big bezels my view just looks wrong if I don't use bezel correction. I get 60 to 110 FPS with my rig, using Surround (1 Camera view) and with Helios running on the outer 2/3's of my left and right screens. Having to run mostly medium/low graphics settings to get those frame rates which is why I was curious. My rig:- i7-3930K @ 3.8 GHz, 32 GB RAM, 2 x GTX970 in SLI, 450 GB SSD, WIN 10 Home 64 Bit. Built in 2011, so showing its age a bit. Sure I can try it myself but wondered if someone could give me an idea of performance boost beforehand to save me the effort if it's not really worth it. I'm guessing it probably won't gain me that much performance boost at all, which is why I asked.

Out of curiosity, what kind of FPS gain would you get if switching from surround? I've always used surround to enable bezel correction but I would maybe give that up if performance boost was significant enough.

You can find a link here to a forum member's shared copy. https://forums.eagle.ru/showpost.php?p=4236083&postcount=9 Only other place it can be found is with the 2.5.6. beta release. The copy on ED site is still ancient. Doesn't look like they've updated it in years.

Nice to know about the new manual. Always good to have official reference information. I noticed there is no date stamp on the manual download page though. It would be very nice if a date stamp could be added so we can tell at a glance how current the information is. Same goes for all the other manual download pages as none have date stamps. ED, please?

BK117 pilot doing an amazing job in very windy conditions. Give that guy a cigar!

The expression on her face is priceless :D

I remember watching a documentary back when flight sims hadn't long arrived on PC's. It showed a guy who'd built a complete fighter nose section/cockpit in his garage for his sim and it looked great. He also had a flight suit on, complete with helmet, mask and gloves but as he climbed into the cockpit, the camera panned over and you could see he had a 14" CRT monitor (possibly smaller) perched above the main panel. LOL! As he started flying, you could also see his sim was stuttery as hell. But he looked great and obviously felt great, so it must have been worth it. :D I'm so glad we have much better tech today. Just imagine what the future holds...

I would do it myself but... without access to the full list of functions and their proper usage, all I would end up with is a half baked and inaccurate document and I'd get even more grief for posting garbage. What is scattered on the forum is incomplete and unconcise, so not a good source to compile a list from. I'd have to ask ED to provide me with a list of functions so I could make the document - which is what this post is about to begin with. A simple request for information. It's not like I'm asking for a complete manual on all the editable files in DCS - just for one file which they told us to use. It would literally take them just minutes to post a short text document listing the functions (which will already exist somewhere anyway). Sure, there are functions that are for in house testing only. So leave them out and just list the ones they want us to use. Simples. If that's too much to ask then fair enough, slap me down and rain on my parade. I'll just humbly keep quiet and accept the status quo.

It would be handy if the server browser stated clearly which servers are running stable and which are running beta. Seems there is currently no indication what version is running unless the server creator puts it in the server name or description. That's just adding more stress to the situation if you don't know who's running what. Often puts me off going online to be honest. I'm in the minority camp, in that I only run with stable as I know there are often issues with the betas. I'd love to have the new Ka-50 cockpit but I can wait until the issues are worked out and 2.5.6 goes to stable. I am however of the older generation that grew up without internet or smartphones so I inherently have more patience than the younger generation. How many of you remember rotary dial phones and having to rewind a VHS video tape? The good old days.. lol. Modern connectivity with smart devices and fast internet makes people impatient - they want and expect everything NOW! Unfortunately the internet also provides a buffer for people to feel safe behind. They feel they can say what they want without any real consequence, since they're not standing face to face with the target of their aggression. Would be a fair bit different if they had to be face to face. Anyway, I personally think you should restrict the Beta versions to a select group of trusted testers and force Joe Public to go with Stable only. I'm sure you already know a large enough number of trusted people to effectively test and iron out bugs in a closed and civilised environment. That's my two cents worth.

No worries. Glad you got it going. Happy flying :thumbup:

That's exactly what I'm on about - small snippets of advice, scattered across the forum and we have to search for ages to find them, then trawl through often lengthy threads to find the bits we need. There can't be a huge list of functions available in the autoexec.cfg file, but from what I can make out, they can be very useful for a number of things. So, why make us search and use trial and error when it would take them literally just minutes to outline them in a simple text file? I don't get it. Far too often we get the standard "search the forum" answer for stuff that could and should be easily documented.

When you said you can move the mouse "down" onto the second screen I'm assuming its setup in Windows to be below the main screen. With that in mind, had another look at your lua file and realized that:- 1. You had both left and right MFCD's set too big for the space you have available. That is, you only have 800 pixels screen width but you'd set them to be 525 pixels wide. That equals 1050 pixels and you only have 800 to play with. 2. Your X coordinate for the right MFCD was set at 800, which is where your screen ends, so it would render off to the right of it. 3. Your centre MFCD had coordinates for out in space beyond your two monitors. On an 800 x 600 screen you only really have room for two MFCD's at maximum 400 x 400 each, so I've made a new lua file to suit your setup and display only the left and right MFCD's. Should hopefully work and get you going. Sorry I didn't pick up on all the above first time round. My_setting_3.lua

I'm assuming you followed Guppy's instructions and placed your second screen below your main screen in Windows monitor setup? If so, your overall resolution should be 1920 x 1680 (i.e. 1080 + 600). If your monitors are side by side in Windows then your overall resolution would be 2720 x 1080 and your coordinates for MFCD's will be different. What aircraft are you flying, F18? What exactly are you trying to display on your second monitor? Just left/right MFCD's? I don't actually have the F18 so I'm not familiar with setting up viewports for it but I'll try to help as much as I can. I know the methods but just not that particular aircraft. A couple of my friends have the F18 however so I can get some info from them if required. With some luck, some other kind soul who is more familiar with the F18 might pitch in and help as well. PS. I see Guppy was using Ikarus. It's not that easy to learn so you might want to have a look at Helios as an alternative if you want panels, gauges, buttons etc.