Ramstein

A10-C my auto start is bugged too... it used to work up until a couple months back... thought it was my Saitek X52 Pro HOTAS.... but cannot find the problem.. all other aircraft seem good.. Been a real PIA. I posted about this before... but I was hoping this controls reset and patch helped... still not right. seems to be only in Open Beta. We as a squad only fly OB for now. server-20181016-124808.trk

All your base belong to us. (me). If you are tired of these issues, please send me your (really good HOTAS... as mine is totally worn out, and could use yours if you quit… thanx...).. back to the issue at hand....

my rb-75 weapon and crosshairs have not worked in a while. I don't know when they stopped working, but it has been a few weeks at least, maybe longer. I don't know what broke and when, I have been trying to find out what happened. I don't have vr, track ir, etc. I just use joystick and keys. I can slew the crosshairs, but they do not open/close/lock :joystick:

I found a fix that worked.. had to go into the computer registry and delete some entries, and they were rebuilt in windows... https://www.flightsim.com/vbfs/showthread.php?260158-Saitek-Pro-Flight-Yoke-LEFT-DRIFT "To recalibrate in Windows, first remove the USB plug for your controller from the PC. Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. Type regedit and then click ok. The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name. +HKEY_LOCAL_MACHINE (CURRENT_USER if on Vista) +System +CurrentControlSet +Control +Media Properties +Private Properties +Direct Input Delete any folder inside the Direct Input folder that begins VID_06A3. Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. Now go to Control Panel > Game Controllers > Properties to check the axes on the test screen."

I found that in the controls, the one that says 'Syncronize controls with HOTAS' at Mission start was checked causng the throttles to be frozen on off. I must have checked these at sometime, not knowing the problems this would cause with not being able to run some aircraft. this evil setting must be never used if you have a Saitek stick.

thanx, will look. I don't know if it is just my eyes,,, but to me it is really bad... :joystick:

still doing this crazy horrible beeping sound in FC3, when hosting..... really bad... is anyone going to try to fix this?

I cannot see the green hud info in ka-50. How to change to other colors? thanx:joystick:

anyone have a SA-342M Gazelle Helo they might consider gifting. Maybe have an extra for whatever reason? Thanx. :joystick:

Viggen: Should the commands T0, T1, and TV be set on Buttons, Hats, etc? which work better? I still have problems slewing the crosshairs, then locking them with the TV Fix, etc... can't see the crosshairs very good... Then I put the crosshairs over a target on the radar and try to lock it, and often it will not lock... Windows 10. Etc. I have a Saitek X52 Pro with the latest Saitek software, use profile and in game control panel too. Computer works great. Just never happy with the Viggen commands. Always glitchy. Tried both putting in the coordinates in the CK-37 computer, ahead of mission, and also trying to set up the IP point on the fly by locking the point and slewing to the point on the radar. The To, T1, TF, Fix, etc, are a pain. I just download the Combat File utility to use with the cartridge. I have not had a good test yet with that. The entering of the AO, A1,A2, seem to work fine on the 2 stage trigger. But the F1, Fix, etc are a real PIA. Maybe the stick, maybe better with buttons on the stick, maybe the hat to flaky, maybe age and sloppiness of the Saitek X52 pro stick make it not work correctly. I have spent too many hours and am getting fed up! Ideas ? I have read lots watched videos, asked questions... Maybe those with the same hardware and software have hints for better results? Thanx... :joystick:

here we go again and again with ctd, even with latest patch. log file attached :mad: I have an easy Viggen multiplayer mission, several Viggen, each ready for a different weapon. practice only one weapon only one at a time by myself. Loaded cartridge, loaded BK-90. Took off then CTD. Just got done flying a Viggen with RB-04E and hit ships minutes before. it's getting confusing, the CTD's. Just trying to say these are just easy new missions with just Viggen to practice using the air-to-ground. Didn't happen until a about 2 patches back. dcs.log.txt

this driving me crazy too.. T1-TV, and slewing with a cross I can't see even when set to proper settings,, if I set the radar to BER I can find the cross easier, but it is almost always hidden off the scope.... then slew it, but lock it before it jumps out..... not sure if it is because of the old Saitek stick, or what not, wish I could enlarge the cross, change color, etc. to see it... it seems that in the past a lot of stuff on this aircraft ( and others) worked better before the massive upgrades and patches... of I have to spend a lot on a new stick... (need new stick, but not until I have lots of extra cash.... LOL.... sad :( ). :joystick:

What/Where is the file with the crosshairs? is it an image file that can be tweaked to be made bigger, brighter, change colors? I looked, but no luck.... (maybe it is script generated.....) thanx

re: Viggen: Can the Slewing Crosshairs be made brighter? I can barely see mine and even when slewing around cannot see/find them... unless background is dark. Is there a way to make them brighter/easier to see? :helpsmilie: Thanx

My Viggen had only a flat tire, would not repair on airfield with all equipment. :helpsmilie:

My Viggen missions CTD also. running as multiplayer. I tried many times. btw.... in the threads below me they say they have a lot of bases, farps, pads... well I didn't have them.... maybe one or two bases... and I airstarted.. I just have an easy map setup to practice Viggen flying and weapons. … I have no clue about adding farps and airbases and ctd's increasing… dcs.log.txt

I flew again today.. the tv screen is just like what this thread says,,, plus nasty lines appear like the old tv's from the 1950's when a tube goes bad. washed out, bright, or too dark,,,,, sometimes, you get lucky and it looks decent for a few, then goes back to crappy and can't see. Yes, this is probably listed in bugs, but why broken now after all those years of a decent screen to target targets. Sad that it could take months to fix things that worked many years until some bad code in some updates. I don't think it my computer, as I have pretty much good equipment and software. Plus there are many other pilots who have been affected by these issues. I am happy there are some of us here who can tell those who can help in better words and descriptions that I can, about what is wrong. update: Nvidia changed V-Sync to adaptive, almost everything I can think of is maxed out, but no Overclocking of anything. it seemed to have helped with the IT-23VM TV monitor.

I used to use backspace to reset it...… but now.... the problems with the skval have me really having h a hard time with using it... the bad screen line, terrible picture on screen, slewing, lock and unlock with 'o' letter key. Hope it is sorted soon, 15 years or working good then boom! update: I made some changes t my Saitek stick profile... and it helped a lot..... the screen looks better after adjusting a bit.... I used to do less adjustments and didn't have those issues before... now it seems better after reworking my profile... also I put new Nvidia drivers in.... I still need to go on some more servers and missions.... so...….. thing look better now, but earlier tonight it was all messed up.. will go on more servers and see if it was my settings.. I had no changed my profile in a couple years.... until late tonight.. but, the lights not working or so dim... that one cannot tell if they are on or off should have been fixed by now... IMHO

yes, it is driving me nuts! the screen is horrible, totally broken since a patch or 2, or 3 back.... not sure if it was fixed, but it sure wasn't on mine.... been flying Black Shark since it first came out, this is the first time it was messed up... screen lines, brightness, contrast, distortion, etc..etc...

I tried the anti-lock braking on a runway, not on carrier. I was not happy, going back to regular braking. The braking was too weak and did not slow me like I expected. Not sure if the code needs tweaked or not. Anyone else find the braking lacking on regular runways ? :pilotfly:

it only works on x52 pro version. pictures? no.

Viggen altitude reference setting reversed. Reference line on gauge looks like it is reversed.... when setting reference, or just floating with up/down, the reference line goes down when going up in altitude, goes up when aircraft goes down in altitude.. is that correct? shouldn't the line go up when aircraft climbs, and go down when aircraft loses altitude? I noticed this when setting my key for reference. Or, maybe there is an option to check a box to reverse this reference. I have to go back and look.

Thank you to al that helped in this thread,, I just didn't have the words for what we need.. :doh:

It is not just me, others who fly the Viggen have noticed some problems now with not only the scope (not being able to see correctly, with not being clear) to weapons either hard to lock or not locking, or both.... something bad happened with either patches, updates, or other!

I use 2-sided Velcro to the desk