EntropySG

Hi Andre, one thing I noticed, raising/lowering the gear in the A10C is a very short duration effect. Would it be possible to alter it so you can feel the shaking for a longer duration, pretty much like when you move the flaps, but stronger? :)

Great news! I will buy it for sure!

strange, for me it always worked in INR. Youre sure you set SPI after you switched to INR? but then again, its pointless, as Eddie said, markpoints are our friends :)

holy shit man, that looks stunning. In fact, it looks better than what Ive seen for DCS2.0? :O

I came to the 132nd as a complete noob. Before I joined, I flew all tutorials and Baltic's awesome campaign, so I knew how to more or less operate the aircraft and drop bombs, but I did not know anything about correct procedures. I can only recommend you to join any virtual wing, chances are you will (like me) have an absolute blast learning from people who really know what they are talking about. EDIT: get the warthog, really. get it. Also get track IR, you absolutely need it

exactly. TMS short aft will switch to INR tracking mode. What I do is the following: lock on desired target in point mode, laser on to get an accurate distance reading, TMS aft short to switch to INR mode and make SPI via TMS fwd long. That way, your SPI wont jump whenever the TGP camera loses line of sight for a second, such as terrain masking or excessive maneneuvering. You can either use my method, or do as Eddie suggests and make a markpoint where you slew sensors to for SPI. The way I see it, both methods are doing the same thing, the point is that instead of fixating your sensors on a given point in 3D-space (such as in AREA or POINT track, which will 'jump' as soon as you have terrain masking, because the camera now sees a new area or point as soon as a hill comes into line of sight and fixates on the new object now). In INR (or using a markpoint) you now fix your sensors to a place on the ground (no matter of masking), defined my 2D coordinates + elevation.

But of course Eddie is right make a markpoint and slew to that, that's the way to go :)

Try switching the Track mode from area or point to inertia, then create your SPI. That way it will stay on the place you want it to, even when you loose sight to your target due to terrain masking or Gimbal limit. Might not be the correct procedure but it works for me :)

stunning! I have the same gfx card you have, may I ask whether you canged anything in the nvidia control panel for the DCS profile, or just use the custom settings and set AA/AF in game?

+1000 that was the only way for me to get rid of the annoying microstutters

op, maybe this is not the solution to your problem, but try readjusting your cap/clip such that it points more up, then re-center the camera. I had the problem in the A10 that I could hardly look down enough to access the side panels (where the ILS/Tacan freq is set for example). It had nothing to do with in game restrictions, it was simply the positioning of the IR receiver/clip

When I go crazy on graphics settings, combined with heavy weather, my FPS sometimes drops down to 20, in worst case. Even then its quite playable and there is no stutter at all. On the other hand I always had stutters (mainly when panning the view fast or rolling in for guns), even at 70 FPS before I reinstalled everything on a SSD. So that alone did the trick for me.

mmh I run it with multiple monitors with 2xGTX970 in SLI no problem. both windowed or fullscreen, I get no crashes. I know SLI is working, because I get the green bar on the nvidia SLI indicator. However the indicator only shows when in fullscreen mode. When I go to windowed, I get about the same FPS. From this I conclude that SLI in fact also works in windowed mode (did read many posts stating that SLI never works in windowed on any game, which confuses me)

Hi Baltic, if you need another German voice, contact me :)

+1

Great! Will test it als soon aus I get a chance, thanks!:)

wiped the display link drivers and software for the USB screen from the computer and restarted, no joy.

yeah Im out of luck now. For a test, I disabled everything. No USB monitor, removed surround and just used a single screen, disabled SLI and uninstalled ALL mods via JSGME. good thing is, I get over 100 fps now lol. bad thing is, the crazy input lag persists. Must be something else on my system that interferes, but I cant think of anything tbh

I tried and deleted the folder you specified. That, in contrast to the reset all button did the trick. Now the exports work, but I have a 5 second delay between the actual cockpit instruments and the exports. I tried first at full fps settings, which cause a 20 fps loss (Nvidia driver 9.18.13.5286) and 1/5 fps, which almost has no fps loss. The 5 sec input lag does not significantly change with fps settings. All I can say at this point is that unfortunately your software does not like my system. btw, after a restart of DCS, it went back to screwed up exports, notice how the clock is actually displayed on the MFD? link to picture

Will try when I get home after work tonight and report back! thanks for your help!!

as I said, I did that but it doesnt help. One thing Im confused about. I start up the program and under settings, I basically disabled all exports but the MFDs. Then the problems started, as outlined above, and I simply deleted the entire folder where your program was extracted to. I re-downloaded and executed the program, yet all settings remined (as in, all exports disabled but the mfds). I click 'reset all' and restart the program, but the settings remain. From this I conclude that the reset all does not infact wipe all settings. Im pretty sure my problem with the program is just a bad config file stored somewhere. I will try your suggestion and simply wipe the entire folder (under app data etc) and see if that does the trick

A few weeks later since I got my Jetseat from Andre, and I still smile like a child when I take off in my A-10C. So nice to 'feel' you're airborn, when the bumps from the ground stop after you lift off. Just awesome. I also tried my hands on the Huey and man, with the jetseat, helicopter flying is totally different world! :O

I know your program works because everything was ok when I started it for the first time except fps were bad. I then simply pulled the plug and disconnected the usb screen to see whether the fps go up again. From then on no matter if I start with or without usb screen the exports don't work. Only the fps hit got better when I rolled back gfx card drivers. Again where does your program store its window positions? It's not a file in the program directory since a re download does not fix the problem

diagnostics package

amazing. I rolled back the drivers and the FPS issue is completely gone. :O So far so good, but the exports still dont work. They worked when I started the program for the very first time. Then I pulled the plug on the USB screen to see if that helps with FPS and since then I get only black screens on the MFD export windows. When I resize a few times, sometimes I get a static image back, but it wont display what the actual displays are showing. I deleted the downloaded folder and re-extracted the files again but the problem persists. I assume there is a bad config file in my system now, any easy way to fix it? Where does the program store the window positions? maybe a clean config file can help? I also pushed the reset all button, but that doesnt help