ptako

I have this issue for months. I usually join two or three then same servers. When I run DCS, sometimes I see these servers or I don't. Servers are up and running for sure because most of my friends see them and can join them without troubles. Situation changes randomly. Sometimes after few server list refreshes or dcs restarts server shows up and I can join. Sometimes I just can't see it nor I can join it via IP (Server offline message). Sometimes I see server, can join and if I leave it and try to join again - it disappears from list. Same behaviors were reported by few of my buddies. Are there any chances that ED will acknowledge this issue and plan for fixing it? It's highly annoying when we do preflight briefings, then run DCS and one or two pilots just can't join our server or can luckily join after 20 minutes. It ruins the whole thing:mad:

It's in each module folder. For example, for A-10C you have go to game installation folder: C:\Program Files\Eagle Dynamics\DCS World and then drill down to: Mods\aircraft\A-10C\Doc

Done. Can't wait until you meet your requirements:)

Thans for your action. If I could get it - the license would be given to one of new member of our virtual squadron. Not all of people interested in joining have A-10C and it's blocking them in going deeper into simulation.

Thanks for that! If I'd be lucky enough I'd use it as welcome gift to one of new trainees in our squadron.

Hello, We've been using tanker in DCS 1.5 without any problems. Both radio comm and TACAN works as intended.

Same here. In addition I have exported RWR and clock. Both are not readable. Looks like they're not cleared when next frame is rendered and in effect RWR turns more and more green because each symbol is being drawn over already present symbols. The same with clock. After 10 seconds, the seconds digit looks like bold and fuzzy "8" because all digits are being drawn without clearing previous frame.

I have no problems performing loops or cuban 8. What's important - watch your angle of attack gauge during then monoeuvre and keep it pointing third white area (near "20" value). If you increase your angle of attack more then you will bleed your energy very fast and you'll be unable to finish loop. If you'll keep it too low you'll also loose your speed and fail. If you fly with payload - check it's drag index. Too high will also limit your max speed and performance.

Ptako, Hades, Zorg 3 ship A-10C Poland 4 hours

Nope. It depends if you want to se QFE or QNH. If QFW - just set 0 on your altimeter (or pressure given by ATC) If QNH - set runway elevation on your altimeter.

Nice photos! I've noticed that this Mig-21 has an interesting neighbor on the right side. It's Polish Air Force Lim-2, more often referred as Mig-15. You should definitely go back there and perform another photo session for another Mig. It would make our waiting for Mig-15 module release a little bit less painful :)

I know. That's why I'm trying to force pilots to go through checklists. If there is a way to set switches then i could generata some mess at mission startup to ensure that pilot will go through checklist.

Hello DCS experts! I'm wondering for some time if it's possible to set up some kind of mechanism for A-10C module that: 1) at the end of mission: - will export (and save in file) current positions of cockpit switches, rotary switches etc. for all A-10C aircrafts (separately) - will export additional info such as fuel quantity, weapons and gun ammo quantities. 2) at the beginning of mission: - will check if file with exported data exists for particular aircraft, and if so - it will set switches according to data from file. By default when you begin mission on ramp, all switches are in correct positions (so you don't have to do pre-startup checklist (left console, instrument panel and right console checks)) to ensure you're good to go with startup. My intention and main goal of this mechanism is encouraging pilots to perform correct shutdown sequence when they are already on the ground after sortie. Idea is based on simple thing - if you shutdown your aircraft properly, you will have less work when you'll startup it next time, because all your switches should be in correct positions for startup and you'll only have to check them to confirm. But if you didn't perform shutdown procedure you will have to place every switch to correct position during pre startup checks. Described mechanism doesn't have to work when the mission starts and pilot enters his aircraft. Acceptable solution is also modifying mission file (something like "prepare mission" feature of mission editor) before running it on server. My main concern is if there is a way to read current position of particular switch and to set it back to chosen position by modifying mission file or during mission start. Any hints, advices or ideas are very welcome.

Anyway you should listen to TACAN and/or ILS morse codes to make sure they're on and that you're tuned to intended source. It would solve your problem in this case.

It happens. When you touchdown with too high speed and lower your nose too fast, front wheel will bounce raising your AoA again and because of high speed it might be enough to lift off again. I don't know if suspension is overmodeled or such bounces could happened in real but in game they do. There is one cure for that - touchdown with correct speed. In that scenario even with such bumping you won't find yourself in the air again.