ruprecht

Although I normally update my pit news on pitblog, I'll re-post anything specifically related to DCS here in case it might be useful for anyone. Latest addition: the targeting mode control panel. Just waiting on the 1.0.1 export hooks to get the lit pushbuttons responding properly.

I've not yet installed the patch, are the Lua export changes noted in the patch notes, or in the file, or will this be a separate update? Thanks again

phew! about to run the patch, guess I'll come up against this too.

screenshots, photos and posted configs help, it's hard to determine exactly what you're seeing. Pretty sure it won't be insurmountable. Are you still running the phantom monitor fix exe?

What do you mean screwed it up? Screwed what up? Screwed it up how?

I'm considering getting one of these and coding a little C++ application to extract the LoGetSlipBallPosition() from DCS and rumble either the left or right side depending one where and how much my slip ball is deflected. That got me thinking that DCS could really benefit from this, in terms of generally feeling hits on the airframe etc. Is there any thought to supporting this product in a future patch? Cheers

I really can't comprehend the issue you're facing. I run 3840x768 at a 50:10 aspect ratio and I see no stretching. If you set your config correctly as I described above, and zoom out to the maximum FOV, there is no problem. Screenshots might help. Here's mine.

A good read on mountain flying here.

londo-cat, I mapped the two red-handled levers to left and right throttle axes. Works fine, like a normal joystick axis.

oooh, anything that might help me squeeze out more performance is good. Is there an instruction somewhere on how to do the change?

hannibal: Q6600 2.4 oc to 3.2GHz 6GB DDR2 9800GTX+ Win7 64bit I run at 3x1280x768 plus the 1024x768 abris. performance is ok but not stunning, I'm upgrading the CPU and GPU soon. Not sure what the dll's are, I run stock Nvidia drivers. cheers

I have three of those quadrants, and use one for my throttle controls (bottom left of the pic, red handles). They work really nicely. Hah, I started out as a complete muppet with two left thumbs. You pick up all sorts of things building a pit - electronics, carpentry, spouse negotiation skills, scars....

Haha, functional as in it's wired into the headphone/speaker system, and I can direct the output to either, mixed in with game audio and vox :) Little bit of Ride of the Valkyries now and then, does me good.

That's absolutely sensational Ulrich, my deepest thanks.

Hi, I've just finished building my Targeting Mode Control Panel and was hoping to hook the lit buttons up to DCS's button light states. However, I can't find where in the export those button light states might be found. Moreover, my next panel, the autopilot, I can't find export hooks for those lit buttons either. Can a dev or someone in the know please respond and let me know a) if they are in there, b) if so, where, and c) if not, could I please request that they are exposed in an upcoming patch? The lit pushbuttons are $20 each and I'd hate to think I just wasted $100 because the sim doesn't export the necessary data. Many thanks

Trigger et al, Don't mean to hijack the thread, but I've just finished my targeting mode control panel (image attached) - not my neatest work ever, but it's done. I've had a look through the lua export and can't find state objects for those button lights! is it just me, or are they missing from the data export? I'd hate to have wasted all that money on lit pushbuttons if the data export isn't available for those buttons! Thanks

Rep inbound cypher, thanks for the PMF.

Sensational. All credit to you for your persistence - it does work in the end! Nice looking setup! Fakum, glad you got yours going too. All is right with the world... until my next customer.

There's another that says you should always have at least one of: daylight good weather fuel :) Compared to a blackhawk or huey it's snappy as hell. And remember that in combat you'll be close to max all up weight. Dump all your stores and half your fuel, she'll perk right up :)

Shame that the multiplayer GUI problem with multiple monitors was not included. Hope to see that in the next patch. Simply displaying the GUI only on the CENTER display the same as the SP GUI, rather than spread across all displays, would make life easier for everyone using multiple screens. *edit* For those beginning to hyperventilate, this is not a complaint or a criticism of the patch. This is simply me saying that something I think is important was not included. I understand the reasons why not everything can be done in one patch. So calm down.

It certainly does seem that it's reading a different options.lua. Simple test: rename the multimonitor file, edit the new name into options.lua, then see if that change is picked up in the options screen. If not, you're editing the wrong options.lua file and there is probably a duplicate in the VirtualStore as Fakum pointed out.

I believe, though I'll need to check, that the "aspect" field in the options screen should show your wide aspect, not the aspect of the main screen. So that indicates to me that there's something wrong with your options.lua file, and DCS on load is possibly defaulting to 16:10. Perhaps it's something to do with your Danish keyboard? Unfortunately I'm away from home at the moment otherwise I'd send you some pre-configured files to use. If you can wait until wednesday night (aussie time) I'll do just that. Could I suggest that you start again from a fresh copy of the original, and rather than use your decimal point or comma keys on your keyboard, copy and paste decimal points and commas from within the file to ensure that the text code is correct?

Pull the fuel shutoffs at 130km/h and 200 meters AGL. There, are you worried about a pinpoint accurate approach and landing now? Problem solved :)

Search for view.lua fov modifications to up your default FOV limit to 200. Set your DCS options to 1680x1050, and aspect to 16:10 as you have done. This changes the file "options.lua" - you can check that file directly (using a UTF-8 aware editor like notepad++) to make sure your changes are saved. Also look at whatever monitorsetup file your options.lua is referencing, and check that the main view section there reflects your setup. Finally - important - Use your view zoom keys to zoom right out. Are you running fullscreen or windowed? If windowed, make sure your windows desktop is set to 1680x1050 as well. That should do it - if not, screenshots, photos etc to help people understand what you're seeing.

Having done dozens of these myself, and helped dozens more, I say this with the greatest sympathy for your frustration: It is almost certainly something you are doing wrong. I would be very reticent to blame hardware. Go back to first principles and start again. A scattergun approach, where you try "every combination", doesn't work except by luck. Do it deliberately and precisely. When using the phantom monitor fix exe, you do not need to configure a phantom monitor. The numbers I gave you do not use a phantom. The fact that you are still talking about phantom monitors makes me wonder if you really understand that? Did you scan for duplicate files? Please post a screenshot of your windows monitor setup - i.e. the settings window where you drag the screens around and set "extend my desktop onto this monitor". Can I also confirm that you are not changing anything in the DCS options screen once you've manually edited the files? Please post a screenshot of your DCS options page showing the resolution/aspect/multimon fields.