RedX

+1 Sometimes I feel that the nav lights are brighter than the search light. And the door gunner bug needs fixing too...

Is anyone else bothered by the god rays in rift? They feel quite strong and seem to vary a lot unit-to-unit. Most folks are conserned about the SDE while I am not bothered by that at all. The rays are much more disturbing for me and they were strongly present in vive pro, too, that i tested. What about the other headsets and rift s and reverb in particular? I did not notice rays being mentioned in youtube clips.

I made a quick improvement by using a drop of super glue and an unused orange "nipple" from a Thinkpad laptop, where there is a very small ministick in the middle of the keyboard to emulate a mouse. The Thinkpad came with a couple of different replacement caps on the ministick and one of them is now glued on my warthog ministick. Improved the feeling quite a lot. I've been wondering whether it would be possible to replace the throttle's ministick with that of an old Thinkpad, since they have pressure sensor.

Has anyone updated their TMWH throttle to the new version 23 firmware? Is there any information out there regarding the differences to the old version 20? The new one is available after downloading the new driver software from the Thrustmaster support site ts.thrustmaster.com. Since my throttle is working fine I haven't updated yet, but I'm wondering whether there is any reason to do so. (If it ain't broken, don't fix it....:music_whistling:)

I am not able to save any changes to my MFD Cougar button setups. It always saves (after several clicks on the OK button) a file with the following content only in <user>\saved games\DCS\config\input\a10c\joystick\f16 mfd 1...lua: Yep, the file seems to be truncated and any changes are not saved. Keyboard and Thrustmaster Warthog joystick+throttle files seem to work, though. Very weird. Edit: It seems that I'm having this problem: http://forums.eagle.ru/showthread.php?t=118251 It is also discussed here: http://forums.eagle.ru/showthread.php?t=119755 Any solutions to it yet? Is it related to the problems of the other posters above?

Hi again, Cowboy10uk Not exactly what I wanted, but I just found a quick hack to move the kneeboards from my aux screen (with Cougar MFDs and stuff) to my main screen. My screens are side-by-side, main on the left and aux on the right. The kneeboards appear on the right edge of main screen with the following change: file: ...\DCS World\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua original line #17: local default_x = LockOn_Options.screen.width - default_width is changed to: local default_x = LockOn_Options.screen.height * 1.6 - default_width where 1.6 is the aspect ratio of my main display (1920/1200=1.6). You may want to try to change the default_x and default_y values around to get them to point on your 4th screen. The line belongs to the function update_screenspace_diplacement(), which is used by the kneeboards' "init.lua" file. Weird stuff can be expected if that function is used by other scripts, too. So far didn't notice anything, but I only did a quick test to see if everything looks ok. There may be a more sophisticated method to change the kneeboards location, but I'll let someone else find it. Hope this helps.

Hi Cowboy10uk I have a partial solution for you. I was able to find a way to move the WEAPON and AUTOPILOT status around to my preferred spot. The weapon and autopilot status texts are defined in the following file: ...\Program Files\DCS World\Mods\aircrafts\Uh-1H\Cockpit\Scripts\PilotSight\PilotSight_page.lua I just modified the values inside the file so that the texts appear where I want. The modified file is attached below. And a photo of how it looks on my system (I have 2 monitors: main screen 1920x1200 and small one below that one 1024x768; two Cougar MFD frames are attached with velcro to the bottom corners of the small one and a small keypad is on the top edge). The Cougar MFD keys next to the text are bound to the autopilot functions. Trial & error with the numbers may allow you to move the status text around to the proper place on your 4th screen. Note that the x-axis numbers increase to the left. I hope this helps. Unfortunately, I did not find a way to properly customize the KNEEBOARD location and size. I believe the related files are located at: ...\Program Files\DCS World\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD I tried to play around with some changes in the base_page.lua file, but I didn't quite figure out what the proper changes to scale and move the display to my left Cougar MFD would be. If anyone solves this one out, I'd appreciate it a lot!!!

One more report on 1.2.1.6148 version performance. It appears that on my windowed 2-screen configuration the Nvidia anisotropic filtering setting has huge impact. For years I used to have AF=16 for Lock-On and DCS with no FPS penalty. Now it reduces FPS by a factor of two or so and causes irregularity to smooth motions so that accurate flying is not possible. If set to "Application controlled" or "off" the sim works. Forcing AF to off makes the terrain look quite bad. "Application controlled" reduces FPS only by 1-3 and terrain looks quite ok. Perhaps it is set to AF=2 or AF=4 by the sim? Flying over the coastal towns produces a kind of time jitter on the graphics, perhaps that is what you call microstutter? FPS remains steady but the movement of the terrain viewed to the side when flying makes ~1Hz tiny jumps on otherwise smooth motion, as if to catch up some lag. Total graphics memory consumption (reported by GPU-Z) is ~900MB on start of first SU-25T quick mission (medium textures, high scenes). GPU utilization is steady 99-100% all the time. Pre-rendered frames=1, triple buffering=off, vsync=off, windows aero on. Hope this helps.

My apologies for not posting the solution. It's mentioned above but not clearly. The sound problem was caused by the RAM chips. Keeping them close to stock speeds while overclocking the CPU worked fine. A few months after posting the above I replaced the memory chips and never had the sound problem since, even when overclocking. My other problems (graphics glitches, crashes) were solved by going for 64bit Windows. If the source of your sound trouble is the same as mine was, you may be able to narrow down the crackling sound issue to the RAM chips by underclocking your system, memory only, or testing with a chip set known to work well. Wish you luck.

I don't know if this is related, but I'll mention it here anyways... I had problems when I tried to reassign the throttle keys. After assigning them, the keyfile had wrong numbers in the up= .. and down=.. lines for throttle control. Replaced the numbers with those from the original keyboard file using Notepad++ and it worked (sorry I don't have the correct numbers here right now). So if you've made changes in the key assignments it is maybe worth checking the nyumbers for throttle control in the key file in My Games folder (Win 7). Also make sure that no other software or drivers is interrupting your keypresses.

LOL !!! I definitely want the animated cigarette-smoking pilot at start-up in the next patch! It would be legendary! :rotflmao:

Hello It seems that the problem I had with DCS-A10C 1.0.0.9 earlier has now appeared in BS2, too. I use two monitor configuration with 1920x1200 as main screen. ABRIS and SHKVAL are exported to 1024x768 secondary screen. Total resolution in options is 2944x1200. Secondary screen is on the right. When I join multiplayer game, initially the names of the players are visible and I can see who occupies which slot. But if the list of slots is long enough to introduce a scroll bar, the names disappear and turn blank everywhere once I touch either the scrollbar or click any of the slots. I believe this thread is describing the same problem: http://forums.eagle.ru/showthread.php?t=78990 Now quickly testing with DCS A-10C 1.1.1.0 this problem seems to persist in that, too. Same engine, I guess... Using Nvidia GTX 460 on W7 64bit. Latest drivers. If someone has suggestions as where to look in the .lua files for a fix, it would be appreciated. Thanks.

Is the ALT-TAB trick applicable when using windowed mode or only fullscreen?

Now all we need is the exact method to also export PVI-800 digit display, radio channel, etc. to the other display next to ABRIS and SHKVAL just like in A-10C :-)

With a lot of expensive hardware, I think the easy option for you is to go for the full download version. No messing around with old versions and you support high grade sims.

My quick guess is that the sim engine is running on one of the two CPU cores you have. Thus the second core has some free time every now and then after handling the rest of the stuff the windows is running and the total percentage is below 100%. Nothing to worry about, the sim is using as much resources as it can.

Did anyone find out yet how to turn off the ABRIS and Shkval displays in the 3D cockpit when using multimonitor setup in order to increase FPS? I can't seem to be able to figure it out. Something has changed from the A-10C config files. EDIT : I found it !! In order to disable the in-cockpit ABRIS and Shkval displays when they are already displayed on external monitor(s), go to DCS Black Shark 2\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua and edit lines 31-32: purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW, into a single line as follows: purposes = {render_purpose.HUD_ONLY_VIEW, Didn't notice any problems yet. Maybe later :-). ABRIS_init.lua and SHKVAL_init.lua need no tweaking now.

This seems like a bug to me. I had the same problem with both master caution light pushbutton and throttle lever up/down commands. I was able to map the keys just fine by manually editing the files under Windows user folder \ black shark 2\Config\Input\Joystick using Notepad++. There are lines with up = ... and down = ... with values specific to "actions" in the simulator. I checked with the functional keyboard commands file in the Config\Input\Keyboard folder, and in the case of master caution and throttle up/down the numbers differ. I replaced the up/down numbers in joystick file with those from the keyboard file and everything works just nicely. I didn't try it yet, but perhaps the "hold to zoom" problem with Shkval can also be corrected by manually editing the up/down commands in the joystick file. I guess "down" is when pressing the button and "up" is button release. Are they? In addition to master caution, I had problems assigning the same joystick key (TMWH stick button 6) for both "gun fire" and "release weapon". I assigned BTN6 in the joystick file for both using notepad++ and it works (my BTN2 switches gun trigger on/off). To conclude, the numbers in my files differed for at least: 1. throttle up / throttle down (keyboard: PgUp, PgDown) 2. master caution push button (keyboard: M) If you find any other assignments with the same problem, please list them here for others, too.

One additional tip: I've found it extremely convenient to map the UFC to a separate USB keypad. Cost about 30 euros.

Eipä sitten muuta kuin että "milloin" :)

Simple. I'm divorced. I can do whatever I want now.:devil: (except when our kid is at my house)

I've applied the easter egg tweak so after ejecting i can hop in a tank and drive around. Then good spot for a tank -when found- can be checked on the F10 map. Of course for mission editing it is not super-duper accurate but quite good. And driving around and blowing stuff up with Abrams is a lot of fun too hehehe...

This looks great :) Is there a way to copy the caution lights panel on second screen using this method somehow?

If the "camera" view size/resolution is less than the screen size (whether using multiple monitors or not) and HDR is turned on, the Sun glare is opaque black effect. In addition, any unused screen space contains random pixel noise and the HDR smears it so that a glare effect carries it over to the rendered "camera" area. Apparently with ATI drivers there is an option to cure this (AA edge detect) but in NVIDIA drivers I haven't found anything that helps yet. This problem is unchanged since beta 4 for me. Screenshot in the earlier post: http://forums.eagle.ru/showthread.php?p=1098342#post1098342

Well, here's one way to mount... It's for the TMWH but I guess it works the same as long as you manage to attach a bolt on the base of the joystick. A 10mm bolt goes through the joystick bottom, a plate, the seat, and another plate on the other side. The plates reduce the wobbling motion due to seat cushion and rounding their corners (to prevent damage on cushion) was the most time-consuming part of the whole thing. It's fairly rigid now. When removed, there is just a small hole & flap on the seat cushion that can be covered by a small piece of tape if necessary. The good thing is that now joystick is center mounted like in the real thing. Throttle lays on a small table on the side. The idea to use velcro to fix it sounds nice, I might try that. See attached pics.