sascha77

I've played it last night and even managed to kill my assigned targets, only to crash into a mountain top in the heavy clouds on my way home... IIRC, there's no AFAC in the mission, just a Spec-Ops soldier on the ground. And in this mission, he'll contact you on his own once you've reached a certain position. So there's no need to use standard JTAC. I guess you could call it "story-driven"-comms ... Kinda like the JTAC-comms in "Surrounded" .. he'll tell you about targets as soon as you're in the air in that mission, but when you try and contact him yourself through the JTAC-menu, he'll just tell you that there's no further tasking available ... Note: I'm using easy comms, so YMMV

^ Great! Do you think an "exported" CMSC would be feasible as well (both technically and workload-wise)? With those 4 elements (2 MFDs, UFC and CMSC) on a 2nd screen, I think the ALT-F1-view would really become an option ... :)

Ohh.. so that means an external scratchpad would be doable with a future release? That would be awesome ...

How can sharing experience with the setup neccessary to *use* HawgTouch and discussing how to minimize the resulting FPS-hit not be helpful? Yes: Technically it has nothing to do with this great app, but people who use it are bound to run into these kinds of obstacles. Why not discuss them right here in the HT-thread where people who are looking for solutions are bound to end up? :confused:

^ Same here Eagle. I had just bought this Gigabyte GTX460 and was very pleased with its performance in single-monitor-mode (had a GTX260 before). But then of course multi-monitoring spoiled her for me ... ;) A good way to keep the performance hit down is to reduce the overall in-game-resolution. I haven't quite managed to set it up that way, but I'm working on it. Check out this screenshot by a wiser user than me over on SimHQ: Edit: Argh.. can't post the pic... Now, I've already reduced MFD-size to 240x240 and I reduced my 2nd monitor's res to 1024x768. Overall in-game-res is now 2944x1080. Hopefully I'll be able to get that down to 2370x1080 with the MFDs laid-out as in the screenshot. But even at 2944 and with smaller MFDs the performance-hit is noticably milder than on 3200x1080 with MFDs on 400x400 (which I ran first). But: I'm still waiting for someone to tell me how to switch off the in-cockpit MFDs and keep the "external"-ones. I'm guessing that would be the biggest help in keeping FPS up.

Opps.. never mind.. just found out about Photoshop's magic eraser .. BTW: If anyone is interested, I'll gladly share the "shrunk" HawgTouch bezels and setting files. They'll fit an MFCD-size of 260x260. It's not that difficult to do, but "fitting in" the OSBs is a bit time consuming... :) Reducing the MFD-size (and consequently being able to reduce desktop-size/game resolution) has helped the performance quite a bit for me. Nevertheless: My GFX-card is now running a good 10°C hotter than with a single-monitor-setup... :D

And another question for you, Dark: I just did a 60% version of your bezels, fit in all the buttons and everything looked great. But: When I fired up HawgTouch with the smaller pngs, the transparent parts just stayed coloured. I checked the RGB values in Photoshop and they were exactly as they should be (255,0,255). I also checked your originals I had backed up to see if there was an alpha-channel PS might have forgotten to save, but nothing... what am I doing wrong..? Note: The only real changes I made were: PNGs: Resized them in Photoshop by 60%, then just "saved" (not "save as ..) left/right XML-files: Entered correct coordinates for every single OSB

Maybe I misunderstand you, but you should be able to set different sizes for the "exported" MFDs in the "Multimonitor-Setup"-file. Underneath the placement coordinates there's the size-values (400x400 by default). Have you tried entering different sizes for the left and right MFD? Say, 250x250 for the left and 500x500 for the right?

Thanks, Dark. I've reposted the question in a thread of its own. This way I figured the devs would have a better chance of finding it.. :) I reverted to my backed-up .lua for now. My changes seemed to cause some weird behaviour in-game and I didn't wanna mess up my setup...

I'm reposting this question from the HawgTouch-Thread, sorry bout that.. :) I'm using a second monitor to display the MFCDs and HawgTouch for the clickable OSB-overlay. Works great. But: Is there a way to disable the in-cockpit-MFCDs and only have the game draw them on the second monitor? Would be a big help in keeping FPS on a reasonable level, I guess. I suspect that it could be done in one of the MFCD .lua files, but since I don't know how and where, I'd rather not start messing with those .. :) Thanks for your input!

Great tool! After fiddeling around with resolutions and aspect ratio I finally got my dual-monitor-setup working as it should. But of course, there are a few questions remaining. Chief among which is this: Is it possible to switch the in-cockpit MFDs off to save FPS? And I don't mean the "Day/Night/Off" switch since that one turns the "exported" version on the second monitor off as well. I don't have SLI/Crossfire, just a single GTX460 1GB and I'd like to reduce the load on the card. After all: With HawgTouch and a second monitor displaying the MFDs, I don't really need the in-cockpit screens. Cheers, S. EDIT: Did some pokin' around and I've managed to disable the in-cockpit-MFCDs (using the MFCD_init.lua-file), unfortunately this also switched the "exported" MFCDs on my second monitor off. I'm not a programmer, but I guess the "render_purpose.GENERAL"-command in there refers to wether the game should draw the MFDs or not. I removed it and replaced it with the "render_purpose.SCREENSPACE_OUTSIDE_COCKPIT"-command (it just sounded right) ;) but no joy: All MFCDs (in-cockpit and on 2nd screen) remained black. Any ideas what I should do and if it can indeed be done?