GregP

Serial #: 09323 Location: Washington, D.C.

While there are numerous ways to do this, Hender mentioned the simplest and most accurate method here: From p.312 of the 1.1.0.9 manual: "TAD Copy, system action OSB 17. This function is only displayed if a symbol has first been hooked. If a symbol is hooked and OSB 17 is pressed, the hooked symbol will be created as a new mission waypoint in the CDU." Although I have to admit, I'm not completely clear on how 'hooking' a TAD object (TMS Fwd short) is different from setting it as SPI (TMS Fwd long) -- it seems like the same thing. Perhaps the difference is that 'hooking' it cues the EGI to allow you to create a new waypoint based on that point, whereas just making it SPI does not.

I use Fanatec's ClubSport Pedals (intended for racing, but work well with DCS) as follows (note that this requires the pedals to be plugged into the PC directly, rather than thru the Fanatec wheel): LeftRudder: Joy_RZ Slider,0,100,50,0 RightRudder: Joy_RX Slider,Invert,0,100,50,0 Wheelbrakes: Joy_RY Slider,0,100,100,75 I got this setup from somebody else on this forum, but I've forgotten who...

FYI this discussion has continued in the Input Controllers forum: http://forums.eagle.ru/showthread.php?t=77788

Yup, admin on both. With further testing I now realize that it's not just my X-Keys: my Saitek Pro Flight Throttle Quadrant is doing the same thing: chorded assignments work fine in Windows, but once in-game, they all get cancelled. If only I'd made a backup of 1.1.0.8, so that I could confirm whether or not it was 1.1.0.9 that caused this!

Months ago I built a profile from my X-Keys Professional that replicates the UFC and parts of the CDU, and it was working fine; but ever since I installed 1.1.0.9, it seems that all of my key presses on the X-Keys, although they seem to work correctly outside of the game, suddenly don't work in-game anymore. In particular, all of the chorded keys get deactivated, e.g. if I have a key bound to UFC "2" (LCTL + LSHF + 2), when I press the key in-game, all I get is a "2" generated, which causes the LAAP Path Hold switch to be activated. I'm using the latest Macroworks3 (1.0.3.2) so I don't think an outdated version is the problem; has anybody else had any weird X-Keys behavior since installing 1.1.0.9?

Sure, I could move the center monitor up and make the problem easier ... but that is exactly why I have this problem: I don't *want* to move the monitor any higher. :) Not just because I'm stubborn, but because my current eye-level when I sit in my chair is slightly above the center of the screen; if I move the monitor up another inch or two, I'm going to really be looking upward at my monitor, which I don't want. And I don't have any way to lift my seat up, either, unfortunately. So that's why I say my center monitor is fixed in position; and since my right monitor can't be moved down (it's already basically resting on the desk, with only a small riser under it), it seems I'm stuck.

Ah, well, if you're on vacation, then sure, give it a try! :) Here's my config.SoftTHconfig: [main] renderResolution=5430x1080 nonlocalFormat=RGB16D keepComposition=1 smoothing=1 debugD3D=0 zClear=1 vsync=0 tripleBuffer=0 screenshotFormat=bmp dllPathD3D9=auto dllPathDXGI=auto dllPathD3D11=auto [overrides] forceResolution=0 antialiasing=0 processAffinity=0 FOVForceHorizontal=0 FOVForceVertical=0 [head_primary] sourceRect=1355,0,1920,1080 screenMode=1920x1080 [head_1] ; Autodetected as \\.\DISPLAY2 at NVIDIA GeForce GTX 580 devID=1 sourceRect=3350,0,1280,1024 transportResolution=1280x1024 transportMethod=auto noSync=0 [head_2] ; Autodetected as \\.\DISPLAY5 at NVIDIA GeForce 8400 GS devID=2 sourceRect=0,0,1280,1024 transportResolution=1280x1024 transportMethod=auto noSync=0 [head_3] ; Autodetected as \\.\DISPLAY6 at NVIDIA GeForce 8400 GS devID=3 sourceRect=4630,0,800,480 transportResolution=800x480 transportMethod=auto noSync=0 [head_4] ; Autodetected as \\.\DISPLAY7 at NVIDIA GeForce 8400 GS devID=4 sourceRect=4630,480,800,480 transportResolution=800x480 transportMethod=auto noSync=0 And here's a[n admittedly poor] picture of my setup where you can see the alignment difference between the side and center monitors: If there's anything that'll get me more FPS in DCS, I'll give it a try. Thanks!

I think I didn't explain it adequately -- by 'image mismatch', I meant that I'm trying to squeeze 1080 vertical pixels into the 1024 that my display actually has, and so even tho the info bar would now appear at the bottom of all monitors, a point-for-point comparison between the L/R monitors and the center monitor would show that the images don't match as you move down from the top (currently, the tops of all my monitors are aligned, with the L/R bottoms being about 25 mm above the middle monitor's bottom bezel). Wow--rereading the above I'm not sure that explanation helped clarify it at all. :) In other words the L/R monitors' images are compressed vertically compared to the center monitor's image and so as your eye moves from the center monitor outward, you notice a discontinuity in the vertical position of say, the canopy frame. If I want to keep everything proportional and I can't move my L/R monitors down such that all 3 monitors' lower bezels are aligned ... my only choice is to just leave things the way they were and give up on seeing the info bar.

A quick, simple answer -- thanks again, PeterP! I tried that and you're right, that does it. Problem is, of course, that my images don't line up across the 3 monitors. Ideally I'd just physically lift/drop my monitors such that their bottoms line up, and then I could just cut the 56px off of the top of the L and R monitors ... but unfortunately my current setup makes this minor change extremely difficult to implement. Thus my only real choice would be to deal with the image mismatch across monitors, and in the end, seeing the info bar isn't as important to me as having a consistent image across my monitors, so for now I'll just forget about the info bar. Thanks for the quick answer though!

I'm hoping one of the guys who've developed the multiplayer and comms menu mods will be able to solve this one too -- I run a 3-monitor config with smaller left and right monitors. The info bar (when in external views) never shows up properly because my L/R monitor heights are 1024 whereas my main monitor is 1080, i.e. the info is being shown outside my viewable area at the bottom of the left monitor. I can see the gray info bar on my center monitor, but I presume all the text is either over on the left monitor or on both the left and right monitors. I've looked through the FUI folder and don't see anything related to the info bar. Has anyone else come across it?

Nice job, looks great!

There is indeed a 3-position toggle, for example here. These are what I used on my AHCP.

Fantastic work here, icemaker, but I think you're missing a critical 'f' above. :)

The DCS Wiki does a pretty nice job of explaining CCIP/CR modes and at least for me, clears up a bit of the ambiguity in the manual.

Agreed! I made these two changes last night and WOW, what a difference, totally worth the 1-2 FPS I think I lost. Thanks Kuky! Regarding 'clutterMaxDistance', though -- after I exit the game, I see that DCS has set it back to 500. Kuky, did you make your file read-only so that it wouldn't do this?

I can't immediately find any prices for it online, but have you thought about making your own, i.e. buying a 22" monitor and getting a touchscreen overlay separately? I did that for a 17" -- bought a new monitor cheap, got a touchscreen off of eBay, slipped it under the monitor bezel, and viola, I had a 17" touchscreen for about 60% of the cost of a native touchscreen.

No, no backlight with the 54-key version. Not really an issue for me, as I never fly with all the lights out. In terms of multiprogrammable, I think what you mean is something like a shifted and unshifted state, or different modes, and I believe the answer to that is no. Although I haven't delved that deep into the MacroWorks software, I'm pretty sure there's just a single definition for each key for each profile created.

The 270.51 drivers have given me a nice healthy 18% FPS boost, which brings me right back up to where I was at with Beta4 (for some reason the release version dropped my FPS by the exact same amount).

I'm using the 54-key X-Keys Professional and it works very nicely: http://forums.eagle.ru/showthread.php?t=70378

No offense taken, I'm in complete agreement with you. That's why I debated for so long, and did so much research on the net, before finally settling on the X-Keys. I wasn't at all happy paying $200, but, given that I imagine I will use this in sims for quite a few years now, and it's so easy to program, and is not sim-specific, I decided to just do it.

I've been debating for awhile whether it was worth buying or building something that could work as a UFC in DCS:W, and finally settled on one of the simplest solutions: buying a 58-key X-Keys Professional. At $200 it's a bit pricey, but its versatility will hopefully make up for it -- an important point for me, as I didn't want to put too much money into something that would be too DCS:W-specific. Programming it is fast and easy, and the keys have removable clear covers under which you can place labels. I used a template from their website and copied little thumbnails of the UFC/CDU/etc. keys I wanted from a DCS:W screenshot I took, then printed it out and cut them up. I've got the entire UFC, the CDU's FSKs & FA & CLR (pretty much all you absolutely need because so many of the UFC's buttons also control the CDU in FUNC mode), all the Navigation Mode Select Panel buttons, the LASTE autopilot function buttons, and the IFFCC switch (which I couldn't fit on the AHCP I made using TigersharkBAS's instructions in this forum). All in all I'm quite pleased with it. Simple, versatile, and feels fairly realistic.

Not only is it a good idea, but for me, was required to stop DCS from crashing to desktop.

This is hugely helpful, thanks! Might you also post your final Excel sheet with the key assignment matrix? That was actually more useful to me because it provided an easy way to determine what keys were still available for assignment to the UFC, CDU, etc.

TigersharkBAS, why not just build one? It ain't THAT hard. :)