bigbear

Hi Hellflyer, Thank you for replying, but I don't understand what you are saying.

Hello guys. I recently had to reinstall everything and now am having a bit of a problem getting my touchscreen to connect to the A10C game using Helios. I had it all working before, but now I seem to be missing something. Essentially, I managed to get the gauges to display properly using the Capt Loz profile. I created a monitor lua that exports all the game data correctly positioned on my touchscreen. My touchscreen is calibrated so that it operates properly -- accepting and responding to touch and mouse inputs OUTSIDE the game environment. I can run the Helios Control Center independently of the game and the touchscreen will enable me to flick switches via touch or mouse. However, when I start the game, the various button or mouseclicks entered on the touchscreen aren't being recognized by the game. I downloaded the various indicator .init.lua files that were posted from PeterP a few years back. The Export.lua is the most recent one from CaptZeen's site and stored it at this location: C:\Users\username\Saved Games\DCS\Scripts I made no modifications to it. In the past, I had followed PeterP's recommendation to modify the last code block of ViewportHandling.lua, but in later DCS A10C versions, I found it wasn't needed. I tried it both unmodified and modified this time, but still no joy. The viewport handling software just isn't handling my input. Can someone please help me out with this?

Perhaps you are being affected by some basic setup problems. A few months ago, I upgraded A10C from 1.1 to the latest version after being away from the game for a couple years. When I did, I encountered many problems because I followed old documentation by PeterP -- which recommended using Helios to create the Export.lua and then manually modifying ViewportHandling.lua. Doing that messed me up for a week. I finally downloaded the Export.lua from Capt Zeen, http://www.captzeen.com/helios/index.asp, along with his other lua files which I simply copied to the recommended locations in DCS World. Of course, I modified the monitor setup .lua as per PeterP's direction. But DO NOT MODIFY ViewportHandling.lua as was done in the past. That will mess things up pretty badly. Also make sure that your touchscreen is not designated as the "main display" in the Windows display settings. The main display should be the leftmost monitor if you have several dedicated to the outside view, or if you just have one monitor in addition to your touchscreen, make it the main display. Make sure you make that designation BEFORE you open the Helios editor and create your Helios profile. Attached is how my Windows monitor setup appears. My touchscreen is the rightmost one labeled #1 in the Windows display setting screen, and my main display is #2. I am also including here the image of how the monitor setup appears in Helios. Note that the monitor numbers don't match the Windows configuration, but that isn't a problem. The main thing is that Helios knows that my main display is the leftmost one when the Helios editor is opened and that this was established beforehand in Windows Display Settings. I hope that it is all as simple as this for you. Make sure to use the Export.lua from Capt Zeen and don't touch the ViewportHandling.lua as was done in the past. If you like, I can send you my two-monitor configuration files, or my current 4 monitor configuration files.

Thank you so much for spending the time on this, Nicolas. You put together a vitally important mod, in my opinion. It is crazy that so much realism is in the game but isn't in something as basic as weapon effectiveness.

Thank you for the link, Erpe. I am glad that others noticed this problem too. This is a badly needed mod. I hope that ED incorporates it into a future release.

Thanks, Jay, that was exactly it in my case. Gadroc also mentions a couple of other things here... http://www.gadrocsworkshop.com/node/48 and although they aren't all Win10 relevant, it may help Gdehanot.

I encountered the same problem when I upgraded my own system yesterday. I suspect that you also upgraded to a faster machine. In my case, various buttons aren't taking effect as well. When playing, activate the CDU and enter a coordinate via the on-screen keypad. Each number I type gets doubled-up in the display line. There is a good chance you experience the same effect. I am not knowledgeable about how the touchscreen works, but it appears that the processor is scanning too fast for touch input. My hunch is that if you click a toggle switch, the processor is reading the switch twice -- effectively reading both an "ON" and "OFF" input at the same time where the second "press" signal negates the effect of the first press. I believe there is a setting in a .lau file somewhere that sets how many times the processor scans for input from the touchscreen each second. That needs to be reduced in frequency. If I cannot find it myself, I will have to post a question to others on the board here. Either way, I will let you know when I get an answer. Or if you find out first, please let me know.

Forgive me if this is the wrong place to post this problem, but it wasn't clear to me where else to post it. Prior to World 1.5, when flying to the second waypoint in the first training mission (Spring), I was able to bomb the patrol with a single GBU38 and wipe out the whole patrol. Now in 1.5, that GBU38 will only destroy a truck and two soldiers. I started the sim again but used a GBU12, which is also based on the MK82. Again, I hit one truck, knocked out a couple of soldiers close to that truck and the second truck - just a few feet distant -- drove away! In reality, either of these bombs cause an explosion killing everything in a 60 meter radius. And yet now apparently these bombs have not much more effect than a hand grenade. Something is seriously wrong here!

I finally got this working. Capt Zeens file was the trick.

After hours of searching and experimenting, I finally was able to get one the MFDs to export. I think the other instruments will be easy. The trick was that I needed to get a good Export.lau file. I found one by a guy called Captain Zeen (http://www.captzeen.com) who put in the coding for that. There is also a guy named PeterP who wrote a good article on the basics -- which I initially got frustrated with because it was out-of-date on some important points. For example, it now appears that I no longer need to modify the ViewportHandling.lua as indicated by PeterP. (Doing so, messed me up for many hours.) But PeterP also provided some important instrument-specific lua's that worked for the one MFCD and I hope will for the others. I will know this weekend when I have more time. Thanks for the code snippet, Sabre-TLA. I will check what you have with what I have from the guys I mentioned. I am feeling optimistic at this point. I sure wish ED would make all of this easy with a simple screen of some sort. They provide the hooks, but now just need a nice interface to make guys like me happy.

Does anyone know how to export viewports in ver 1.5? I just upgraded both A10C to the latest version along with updating to World 1.5 but now am unable to export the viewports so that it can run in Helios. Call me spoiled, but that will kill DCS gaming for me unless this problem is solved. I had some dreams of even building an A10C cockpit, but now it looks like that might go by the wayside too. I really wish ED would make the effort to make the exporting of the viewports easy when they do upgrades. I know I can't be the only one struggling with this. Getting the viewports on another monitor just moves the gameplay to another level.

I made the big decision to go from World 1.2 to 1.5 the other day and upgraded my A10C from some version back in 2012. In the past, it was very enjoyable being able to use it with Helios. Now it appears that things have changed and it is not possible to export instruments to another monitor. Is anyone able to do so? If so please provide instructions or the files needed. I have spent hours fussing with this. Without the exporting of viewports, I just can't see playing this game.

I recently upgraded to World 1.5 and am now unable to export instruments to my secondary touchscreen monitor. I have two monitors both at 1920x1080. I think it has something to do with some changes in ViewportHandling.lua, but I am not sure. Has anyone been able to export instruments with ver 1.5? If so, would you mind sending or posting your monitor file and your version of ViewportHandling.lua? I just can't imagine playing this sim without Helios or some other package that can show my instruments on another screen. Your help would be greatly appreciated. I just feel dead in the water without this.

As the last poster asked, does anyone know if this is available for 1.52?

Unable to export instruments in World 1.5 I just updated my original version of A10C (after all these years) to the latest and also updated to World 1.5 from 1.2.16. Now the instruments won't export into Helios. Is anyone able to export their instruments with World 1.5 to a second monitor? I can't imagine playing this sim without a second monitor.

Thank you, Yurgon, for your help in solving my problem with the mission editor. You were right: The problem was due to those extra folders in the .miz file. (I totally forgot that the .miz files were just zip files.) In fact, I found that just by deleting the DSMS folder, the program took the new DSMS settings. The fact that this occurs at all appears to be a bug.

Yurgon, I am running World: 1.2.16.43180.9-9 and A-10C: 1.2.16.43180.9-9. Attached is the mission file. Thank you for taking the time to look at this. Daves First Mission.miz

Problem creating mission I have created a mission, and in the process, I went to the Payload screen to select/adjust the payload. I then save the mission. When I then click the Fly option, it shows the payload I selected in the Mission Data section on the Briefing screen. However, when I then choose the Fly option from the Briefing screen and actually start the mission, I only have the default payload used in the Instant Action missions. The default payload appears in the DSMS and visually on the wing pods. What am I doing wrong?

I think it is wonderful that DCS has been able to allocate resources for WW2 aircraft. I love the idea that we might FINALLY be able to get a truly realistic flight modeling of aircraft of that era. But, I genuinely hope that DCS will also be able to start to move to putting resources into the combat simulation aspects with good, realistic AI. Essentially, my whole interest in flight-sims from the very beginning in MSFS 30 years ago is that I wanted to feel what it was really like to have been a combat pilot even though that wasn't a combat sim. Just flying a plane and looking at scenery does nothing for me. And I don't want to fight a P-51 to P-51, either. Let me fight a death struggle with a 109 or see what it was really like to take on a bomber formation. I want to feel the true essence of what combat was like, almost like watching the old movies during my childhood -- that it be a true immersion into the event. I want to be able to spend the time in the study of the aircraft, but I also would love to come as close as possible to experience the images, news, and sounds of the period, and truly feel the terror of what the real thing is/was. In other words, I don't just want to master the controls. I want to come as close as possible to experience what a fighter pilot went through. I can see that not everyone wants this, and yet I personally would like it if DCS could eventually provide it. I want to just let DCS know what I like because I doubt I am alone in these feelings. I don't feel that experience yet with DCS, but I feel they can eventually provide it just because they have such an attention to detail. Of course, what I yearn for is really beyond what any company could really provide, but I think DCS may be best able to come the closest to it if they put their minds to it. So, please DCS, continue to simulate the aircraft to as close to realism as is technically possible. But please, put some more resources into simulating the terror for me. Help me think I am really there.

+1

I sure hope that DCS did a deep survey of what truly motivates their customer base. Did we tend to buy this game as a realistic combat simulator or just as a flight simulator? I can see from this thread that there seems to be some enthusiasm among the non-combat crowd. I love what I see in the Nevada graphics, but to buy a simulation of a combat aircraft and just fly training missions has ZERO appeal to me, anyway. I want DCS to succeed, and MAYBE I will buy the Nevada update just as a donation to keep them alive to help ensure they use the same technology in a future project. I was hoping we could at least see the Georgian terrain updated with it. Sadly, that is not going to be the case from what I read here as it means a total rework. Maybe this Nevada upgrade will help keep the current customers happy. But, I know that new customers are needed as well. And my own gut feel is that new customers who buy a combat aircraft software package want a realistic combat simulator, not more of the Microsoft FS type of thing. I know I sure do! I hope Nevada won't turn out to be a financial disaster for DCS, but I have some very bad vibes about it.

Well, that's certainly different than the way I have been doing it, Smoky! I have been bugging out of there as fast as I get a threat indication, not continuing on to see aaa fire or a missile launched at me. Interesting, as I would have thought that approach was way too risky.

Thank you for your quick response, Smoky! Great ideas there! I am seeing that I can more-or-less evade the threats, but trying to find them is extremely difficult after I have taken evasive maneuvers. I just find myself scanning and scanning forever and coming up with nothing. Is there some special technique that I am missing in this regard?

Well, I have finally finished the first training mission -- after dozens of times trying to learn various aircraft/weapons features. Now, when I tried an instant mission and get into a more involved combat situation, I find myself confused about how to deal with threats. My question is this: Say I am flying into an area and I suddenly see the threat indicator light up. I see that it is coming in at 30 degrees, but I immediately turn and fly as quickly as I can toward a hill in the opposite direction so that I can hide behind it, and from there, get out of range the best I can. Now that the radar warning has stopped, all I know there is a threat somewhere back there, but nothing will show on the TAD, of course. Is the idea now that I simply start flying around trying to find the baddie with my TGP? I find myself scanning endlessly over vast areas and can't ever seem to find anything that way. I feel like a real pilot would have some sort of logical system for zero-ing in on the threat efficiently, but I can't figure out what that system is. I feel like I am missing something important here. Can someone help share some combat tactics regarding the way he deals with threats appearing on his display?

Pause button I am still new to the simulation and have problems finding targets within the MFCDs. I think I read somewhere that there is some button for newbees like me that I can click that will pause the game motion, but still let me mess around with the MFCD targeting, and yet I can't find it anywhere in the docs. Am I just hallucinating, or is this button for real?