Toastie

Hi, I recently installed patch 1.1.0.9 after a break from the sim. There's no change to my rig. There's good news and bad news in 1.1.0.9: Thus far I have yet to experience side console label loss in the hour or so flying since patching. On my most recent flight (the stock 'free flight from runway') I lost the HUD labels (figures and letters), but the lines and reticles remained. This appeared to occur not long after I alt-tabbed out and back into the game. I will provide further updates in due course. Razvedchik

This got me thinking abit about non-game-related factors. I use Aero in my Win7 64 and that gives the GPU a little to think about. I also have two monitors (which I should have mentioned previously, sorry) - one 24" and one 19". I normally use the 19" monitor to display my MFCDs. Using GPU-Z to log VRAM usage, I tried a number of different combinations of monitor/aero usage to see if the console labels stay or disappear (I didn't test for HUD or MFCD labels on this occasion, as they normally take much longer to go). It wasn't a very scientific test, but I tried to remain consistent across all iterations. The normal 'cause' of the labels going for me is switching to an external view and then back into the cockpit again. All tests were carried out using the stock 'Weapons Training.miz' in the current game version with latest nvidia driver 270.61 on my PC (specs below). Here are the results: Aero + 2 Monitors + High Detail = Labels gone (peak VRAM usage 766MB) Aero + 1 Monitor + High Detail = Labels gone (peak VRAM usage 766MB) No Aero + 1 Monitor + High Detail = Labels gone (peak VRAM usage 762MB) No Aero + 2 Monitor + High Detail = Labels gone (peak VRAM usage 766MB) No Aero + 2 Monitor + Medium Detail = Labels gone (peak VRAM usage 764MB) No Aero + 2 Monitor + Low Detail = Labels remain (peak VRAM usage 763MB) No Aero + 1 Monitor + Low Detail = Labels remain (peak VRAM usage 626MB) In the tests, I took off, flew around a bit, shot up some innocent civilians' houses and other buildings in the base area. I toggled the F2 periodically and back to F1, it didn't always cause the labels to disappear first time, even on higher detail levels, but in those levels it always happened at some point during the flight. In the two cases where the labels just wouldn't budge, Aero was not running and detail was set to Low, the comparative VRAM usage can be reasonably attributed to the extra monitor displaying the MFCDs. I won't get to carried away with analysing those results here. Maybe you can draw your own conclusions from them. Regards, Razvedchik Q9300, 8GB RAM, Asus GTX 460 TOP 768MB, Win7 64, TrackIR5, X52 Pro, dual monitor (24"+19") Edit: I know it's a different beast entirely, but with the same rig DCS: Blackshark's peak VRAM usage is 663MB on full high settings with 1024px resolution cockpit... just saying.

No Joy... I have now set all of my settings to low or medium and have set the cockpit resolution to 256, yet the game still chews up an average peak of 762 of my 768MB of GDDR5 VRAM, resulting in the loss of these labels. If indeed this is the real cause... If it is, it begs a few questions: 1) Why does my friend, who has exactly the same graphics card as me not get these disappearing labels (on the same settings)? 2) Why does turning the console lighting up return the console labels to existence without affecting other graphical performance (ie causing MFCD or HUD labels to disappear instead due to lack of VRAM)? 3) Is there a way of cycling or refreshing the MFCDs and HUD in-game to return the labels when they disappear? 4) Will there be any action taken to address the game's VRAM usage for users who don't have graphics cards with more than 1GB of VRAM? Thanks, Razvedchik Q9300, 8GB RAM, Asus GTX 460 TOP 768MB, Win7 64, TrackIR5, X52 Pro

Just to update you on the situation here post patch... The 1.1.0.7 patch made no difference to the label problem. My wingman has exactly the same graphics card as me and doesn't have this problem (he did briefly but it went away quickly). I matched my in-game graphics options exactly to his, but this too made no difference. I have recently downloaded and clean-installed the Nvidia beta 270.51 drivers for Win7 64 and sadly that has yielded no improvement either. Razvedchik

Hi pilots, I only got DCS: A-10 the other day and it's the patched release version. I also own a GTX460. I am using TrackIR 5. I have been getting the missing labels problem in all circumstances. A first it was just the consoles that went and normally it was in 'low attention' situations, ie while looking at an external view or while looking away from the consoles. Gradually this issue appeared to affect both the MFCDs and the HUD. Strangely the Front panels are not affected. I tried alt-tabbing out and back in again and pausing whilst doing so. I have tried using different cockpit texture resolutions to no avail. Looking on the forums it seemed that getting the latest version of the Nvidia drivers might fix this. It did not. Looking down further through possible solutions, using the console lighting to fix it did work for the console labels, although not unfortunately for the HUD/MFCDs and I noticed that the problem with the consoles reappeared on shutdown when there was no more power to the console lighting. I would show you screenshots, but they look no different to the ones already posted here. Here's hoping that another voice will hasten a fix for this issue. Regards, Razvedchik Q3300 3.0GHz, GTX460, 8GB RAM, Win7 64 Saitek X-52 Pro, TrackIR5

64-bit 6.6.6.9

FIXED ***FIXED*** I just created a completely new SST profile from scratch. I mapped the mouse-click for flicking switches to the clutch button for convenience. The mouse button is now my Flare release. I'm pleased to say that the creation of a completely new profile also appeared to resolve the original issue with some keys/buttons losing their function! Thanks to all that chipped in with advice. These forums have provided me with lots of passive information in recent months, but it's even better to get active help. :thumbup:

@Sarge It was just that I couldn't find the 'mouse fire' in the mappable controls. Is there a setting in the game which enables/disables the use of the mouse on the joystick?

@Deigs I always have the game in simulation mode and the controls on ka-50 real... is there another way? ;) Well, it must be something kooky going on with the SST software because I recreated an in-game profile which works (particularly those bits that weren't - TV TGT +/-). Just to see if it made any difference, I set the toggle switches in the SST profile to 'fallback' mode and ensured the in-game assignments were the same and then tested this configuration. It didn't work. I've gone with Sarge55's solution then... ditch SST. One slight problem with that is that TrackIR5 arrived today and I wanted to be able to assign the throttle mouse button as the mouse click to flick switches etc in the cockpit. Maybe I missed it, but it doesn't appear to be mappable as such in the game's controls. Anyone got any ideas?

meh I did a further test on my issue this evening. The previous two keyboards I'd tried were PS/2, so I thought I'd try a USB keyboard to see if there was any difference. When I loaded the mission that i've been testing this on (Clear Tkvarcheli), I found that the comms worked and so did the Shkval zoom x7/23. On this occasion, however, neither of the TV tgt sizers worked (previously only the TV tgt - had worked)! Just for giggles, I went back to the SST profiler to switch the TV tgt +/- around to see if there were any improvements - neither worked on either keyboard or joystick. Again, all assigned keys appeared normal in the SST profile test page and appeared correctly in the MFD when I attempted to use them. Perhaps a corruption in DirectInput? (bear in mind I reinstalled DirectX with the game's reinstall). I'm getting a bald patch with all this head scratching. @Sarge55 Your idea about ditching SST is sounding better all the time. Oh, since I should have done this in my OP, here are my system specs: Windows7 (64) Intel Q9300, 8GB DDR2 RAM, 8800GTS 512, 24"+19" monitors, X52 Pro, MS Wireless USB Mouse, USB Kbrd (now).

Thanks Thanks for the reply, Sarge. I created a new profile, as you suggested, mapping only those keys which I knew to be non-functional. I then activated the profile and loaded the game. I loaded a mission and tested the keys and their mapped equivalents (the toggle switches and button C). I'm afraid to say it did not work. One strange thing that was apparent was that the ] on the keyboard functioned as 'TV target box -' and the # key, below it increased the size of the TV target box, even though neither the game nor the test profile is mapped that way. A bit of a head-scratcher.

Hi all, first post so please be gentle. I've been playing Blackshark for a few months now without any dramas. I got an X52 Pro back in April and have had no problems with it. Yesterday, I sparked up BS for a bit of practice and as I was playing (the game seems to be working just fine) I noticed that the following keyboard presses (and their associated X52 Pro mappings) did not work. # (which for my keyboard layout is the comms menu) ] (TV target box increase) - Shkval x7 zoom = Shkval x23 zoom I didn't notice any other commands that didn't work. Here's what I did to test the functionality: 1) Test keyboard in Windows notepad - no problems 2) Test keymappings in Saitek profiler test page - no problems (all mappings 'missing' in the game worked ok) 3) Changed the joystick profile for BS so that other commands were used instead of those missing - the other commands worked fine on the assigned buttons/switches. Here are the steps I have taken thus far to remedy the situation: 1) Changed the keyboard. 2) Reinstalled DCS: Blackshark 3) Reinstalled Saitek Profiler software 4) Reinstalled X52 Pro drivers (including Direct Output) I've had a good dig around on the forum, but can't quite find anything this weird. I'd appreciate any help or guidance you guys might be able to provide. I want this working properly for when my TrackIR5 arrives next week! :) Thanks!