HeadHunter52

Sounds like the Dogs of War server, running "King of the Hill." The circle is a ring of towers and derricks surrounding Poti. Is that where you were?

Yup, what T-Zone said. That's what I had to do. The other route, if you aren't using DSR, is to set your monitor to a high resolution, open DCS and switch it to a LOW resolution, then go back to the desktop and return it to normal. You should then be able to go into DCS and match it.

Watched my SysRam values on the G13 while flying tonight. The more action, the faster it fills up. Locks and crashes in the mid 90% range. It's like watching a count down (or up).

Wow. I moved my drive into a completely different machine. New CPU, MOBO, RAM, MAC.... ...and no reactivation. Oddly enough, I didn't need to reactivate Windows, either.

I think you'll like aluminum skin better. I was wondering about the plastic and its flexibility.... That's a great looking pit.

"Summoner's Rift"? Naaaaa That IP? Double naaaaaa Come an git it ct! Lotsa love at the real DoW TS....

I use the frame counter from ShadowPlay in GEForce Experience. Works like a charm windowed or full screen.

I didn't have any issues in SP except for resolution issues of my own making.

Might need to deny "player" rights to fly in any capacity. That'll keep the servers up with legit names?

Ya know, now that you mention that, I believe I experienced the same thing. Maybe too many people with the same name confuses the logic a tad???

Logitech's page lists a gaming download for that stick, but when the details are opened, it doesn't list it. I'm not comfortable with scripting, either. It's not a huge deal, so I'll wait for now. Thanks for the suggestions.

:book:

Well, that's the thing. I have a G-13 gamepad. The software for it won't recognize the Attack3 - too old I guess. There is a software package for the Attack3, but I'm not sure if it will muck up the work for the G13. I was hoping to find a work around that I mighta missed before seeing what I might hose up with the other route.

Hehehe. That's right. We've waited a long time for 1.5 and the upcoming 2.0 glory. We can wait for, and even support Mr. d0o0m in, his faithful and awesome work. :D I'm good with it.

I have difficulty seeing certain things. I have three sets of glasses. Used to have 20/15 corrected, but workng on a monitor now is increasingly difficult. On the DoW server, flying with good pilots, I would have difficulty seeing what they clearly called out. Directing my eyes to a plane, I might see it. I might not. Sometimes I'm looking at the thing and it disappears, yet they still see it, sometimes from BEHIND me. So, bad eyes. Check. Average display? Umm... yes. CHECK. I have 2 things going against me so, if I can gain an advantage that puts me on par, I'll freaking take it. For all I know, my particular hardware arrangement creates a bias against spotting as well as what my eyesight could do on a better system. There is no way to ensure everyone has the same beginning setup, the same results or even a "realistic" experience. I do find it a little funny though. Those with the killer rigs might now have to fly against opponents that have traditionally had a spotting disadvantage, or complete spotting negation (like me), yet now can bring their game up to competitive levels. I don't see how that is a real issue. Well. Kinda. Yeah.... I can see how it is an issue, but it SHOULDN'T be. I set the option for better visibility. I was seeing planes at distances that certainly feel like those at which other pilots in the squadron have called out bogies before. I was happy with it, and not concerned about being superman. Hell. Plenty folks fly zooming in on things to, and THAT certainly isn't realistic. Do we want to do away with that little feature about which no one complains?

I want to use Push ToTalk in ShadowPlay so that my voice (and room sounds) are recorded only when I PTT for TeamSpeak. Using the "always on" setting works fine, and I get my voice recorded. ShadowPlay will not recognize any joystick input when setting the input trigger. It only looks at keyboard input. So, I cleared the DCS assignment for the "T" button. I then assigned the com PTT function to my stick and verified it took. I then also added the keyboard equivalent on the same row, using T. So, T and button 3 from the stick are in the same row. I hoped that pressing button 3 would also trigger T, and get the PTT function going. No joy. If I press T on the keyboard, the mic indicator appears and my voice is successfully recorded. Is there a known way to press a joystick button, causing a trigger of a keyboard button that ShadowPlay will recognize?

Yup. Noticed that, too.

I'll make a donation to the server fund to get you some coffee.... :D

Thank you sir, for the clarification, and overall excellent moderation. :thumbup: And may I say, dog gone, those were fast replies!

Shuttle cock is heavily weight biased forward, with a large drag effect rear. An arrow is more closely related to a powered missile as far as weight distribution, but it is also weighted front, drag and stabilized rear. Missiles are entirely different, and each will have its own ballistic tendencies. They were not designed to fly without power and in most cases, guidance. I wouldn't expect them to fly straight and true except by accident.

I had the expectation that it would be functional, but no go. Not a loss to me, since I could find what I needed without too much trouble before 1.5, but it would be a nice lil gift.

So, if model visibility is enlarged, it'll help me see better?

What is the name of the Server in the MP Server List?

You'll get it, Chief. I have total confidence in you.

"B-17" on Intellivision