GregP

Just view it in Chrome, and allow it to auto-translate for you.

Thanks for the interest, guys. Looks like I've found a taker but if it doesn't work out I'll let y'all know.

I got these about two years ago for the DCS: A-10C setup I was building, but then eventually moved to a touchscreen-based setup where I don't have any need for them anymore. Since they're fairly heavy I'd prefer to not bother with having to pack it up and ship it, and so instead I'm offering these for free for anybody who can come pick them up from me in DC. They're in perfect condition, with no problems.

PeterP, amazing as always!!!! Will try to test this out over the weekend. Thanks again for your persistence!

Any chance you might like to repost your writeup over here? SimHQ is blocked for some of us at work, but the ED forums are niiiiiiice and open. :)

Whoa! Ironhand has joined the DCS world? Maaaaan .... I've been waiting for this day for a long time. Definitely hope you plan on sharing some of your expertise with us via tutorial video -- been a BIG fan of your tutorials since the Flanker 2.0 days. I check your website every few months to see if you've secretly started putting out DCS material...and it's always a letdown! Maybe that's about to change? Wishful thinking?

According to PeterP's post here, both Server.lua and View.lua should be modified in order to get 6DOF working properly. I haven't had a chance to try this myself yet, so I'm not sure if it avoids the problem Smokin Hole mentioned, but thought I'd mention it anyway.

My wife and I are planning a 2-week trip to Turkey, August 26 to September 8, for our honeymoon. We're planning 5 days in Istanbul, 3 in Izmir/Cesme/Ephesus/Bodrum, 3 in Capadoccia, and then one last day in Istanbul. I know I've come across at least two Turkish Lock On / DCS fans over the years (Torwak and Yeniceri) but it seems that both of them are less active on the forums these days. But I was wondering if there are any other Turkish DCS fans who might be interested in meeting up for a drink while I'm there? I always like to meet other members of our community here.

It seems that I, too, was a bit confused about setting SPI via the HUD. I had presumed that selecting HUD as SOI and then TMS-U/L'ing would just automatically make the current STP the new SPI. From what you guys pointed out, after testing last night, and after consulting the manual, I realize I was wrong about how the HUD is used to set SPI. And now I agree with what you guys said -- setting the current STP as SPI specifically requires a TMS-D/L, and cannot be done via TMS-U/L. With this sim you learn something new every day!

I presume your reply was addressed to the OP, and not to me, right? Because while I agree with you, it still doesn't answer his original question -- he did in fact make WP2 the new SPI, and so CH-F/L should have slewed the TGP to WP2.

While I agree with what you guys are saying, that still doesn't quite answer his question, does it? If he advances STP to WP2 and makes STP the SPI via TMS-U/L, and then does a CH-F/L to slave all sensors to the new SPI, why doesn't the TGP respond? Seems like it ought to, regardless of what exactly the SPI is (steerpoint, point on the ground, boresight, etc.). Yes, he could force the TGP to the current STP by doing CH-A/L, but that shouldn't be necessary in this case -- CH-F/L ought to force all sensors to the SPI (which happens to coincide with the STP in this case). Granted, if all he wants to do is get his TGP to point to WP2 just like it did at first to WP1, it is quicker to just advance the waypoint via UFC and then do CH-A/L, avoiding the need to first make HUD SOI, advance the waypoint, make STP the SPI, then slave all to SPI ... but the question is not about the best way to do it, but rather why CH-F/L isn't making the TGP slave to the new SPI.

I'll help out if I can: Male / 36 / American, no particular accent

Also noted in the A-10C FAQ: http://forums.eagle.ru/showthread.php?t=67747 "Q: FAN RPM % does not exceed 82%. Is something wrong with my throttle? A: No. The engine is designed to operate at optimum performance, which is 82% FAN RPM. Also note, that there is a difference between Core RPM and FAN RPM."

I've got a similar setup to what metalnwood describes, but instead of using Helios on the touchscreen, my touchscreen directly renders the instrument panel. This is quite a bit different from just creating your own CDU as the OP is trying to do, but I too tried to go down that path, tried exporting MFCDs, tried Helios, etc. ... and then finally settled on my current config, which is by far the most flexible and intuitive solution I've found yet. So, I thought it was worth mentioning for those who might be interested.

On my TM Warthog, I have a hard time consistently pressing Hat4 'in' rather than 'forward', i.e. activating H4P rather than H4U. As this is a critical difference in-game, in that H4P turns the jammer on and off while H4U starts the selected CM dispensing program, I really need to solve this. But from what I can see in the TARGET Script Editor documentation, there is no way to do what in Foxy could be done by setting a sensitivity to the hat, such that it would not get activated until you'd held it down for the specified amount of time. I'd like to do something similar in TARGET -- assuming that I'd fairly quickly recognize I'd pressed the button incorrectly, release it and try again until I was sure I'd pressed it correctly, and then hold it down. Anybody have an idea of how to do this? Or anything else that would solve this problem?

I have a feeling that some of it is outdated now, and/or needs updates ... but TBH I'm just too lazy to go back and try to figure it out. :) But I'm glad that it's still useful even in it's current state!

Right, that was my thread from last month: http://forums.eagle.ru/showthread.php?t=87650

Excellent advice -- definitely do that, GreyBadger. If you waited for the retail box you'd have to download the 1.1.1.1 patch anyway, so you might as well just install the entire latest game package and then type in your key when the box arrives.

That link will give you lots of info regarding the TO-TO and TO-FROM nav modes, but may not directly answer your question: what you need to do is change your current steerpoint's 'nav mode attribute' to 'direct'; this will cause the EGI to plot a direct route from your current position to the current steerpoint.

coilwinder, I'm using the exact same setup for my Fanatec Clubsport pedals. However, I've noticed that in DCS: P-51D, where the rudder pedals become much more sensitive and critical, this setup has the serious drawback of the fact that if you happen to press both pedals at the same time by accident, you get a really violent yaw see-sawing motion that can easily knock you way out of control. This is an artifact of this solution not being a true 'combined axis' method like Kegetys uses. So, for this reason, you might be better off trying to make use of that 'combined axis' toggle in the Logitech drivers--I'm pretty sure I've seen others in this forum get it to work. Unfortunately there's no such option in the Fanatec drivers.

Hehe...yup, you got it, nice job. :) Apologies for thread hijack. Back on topic now.

Yep, "Add to Cart" over here. And when I order something on Amazon and have it shipped to my office, I then put it in the trunk of my car, drive through a number of traffic circles, perhaps get stuck behind a big slow truck, and then finally get home and park in the parking lot before taking the elevator up to my apartment -- where I can finally open up that package. :)

I'm presuming you're English? So, wow, Amazon says "Add to Trolley" for you guys? That gave me a laugh ... all these little English/American differences are endlessly amusing to me. Anyway, welcome to DCS: A-10C and you can be assured that the code is very stable at this point. I'm sure there must be bugs left, but I've yet to come across any showstoppers as of the 1.1.1.1 patch. This is without a doubt a study sim, though, with Falcon 4.0, as you mentioned, being the closest thing to it in terms of serious combat flight sims to date. But if you're looking forward to Arma3, I imagine you're the type who can handle it. You might want to check out this recent thread from a guy who was just about to give MP a try for the first time and was looking for advice -- could be useful for a beginner. My #1 advice would be: do NOT try to tackle the manual all at once in the beginning. It's just way too dense. A better path is to focus on one particular area at a time (the actual flying; ILS/TACAN; TGP; Mavericks; etc.) and read as much as you can on this forum, on the Wiki, and watch a bunch of YouTube videos about it, before moving on to the next topic. Eventually, you'll have mastered everything. And then at some point after that, after endlessly referring to it, the manual will seem fairly straightforward to you.

Confirmed--mouse scroll does the trick. I was confused because I use a trackball in DCS and knew that I'd tried every combo I could think of before getting it to work...and it turned out that using my other mouse was how I did it. :)

Funny, I had the exact same problem last night and then eventually got it working ... but now I can't remember what I did. :) Maybe something like hold one of the mouse buttons down while you move the mouse left/right or up/down? Or while you scroll the mousewheel? It was something fairly unintuitive like that.