ptako

Hmm... I've just checked it and I'm really disappointed. Our passwords are not sent in encrypted form. They're being sent in PLAIN TEXT in http POST request. Why are you trying to fool us that they're encrypted? THe lock icon near password field means nothing beside when you click it it sends request to http://mc.yandex.ru/clmap/20852101 with some additional parameters. Anybody can check that I'm right using simple tools like Fiddler2 or similiar. When you're logging into digitalcomatsimulator.com there is POST form sent to url: http://www.digitalcombatsimulator.com/en/?login=yes and in sent content there are your login and password put as form fields values: sessid=[hereComesSessionID]&backurl=%2Fen%2F&AUTH_FORM=Y&TYPE=AUTH&USER_LOGIN=[yourLoginHereInPlainText]&USER_PASSWORD=[yourPasswordHereInPlainText] So without use of https our sensitive data (uername/paswords) are just carelessly sent over the internet. Thats not nice, and your post only makes it worse...:doh:

There is no problem in using LL coords in A-10. Works like a charm. Just two buttons pressed on TAD and TGP and you can use LL/MGRS according to your needs. I have no idea if you can change it in CA, but LL is not a problem when talking to A-10s

Verify if you dialed correctly X or Y of tanker's TACAN.

Change assignment from joy slider 1 to throttle axis. Currently you have throttles asigned to this little slider on throttle handle

I did it for Su-25 once. As far as I remember tactical numbers (digits from 0 to 9) are in separate file. It was named something like "rus-code-numbers-ver2.tga" When you replace it with an empty (transparent) graphics file - numbers are not showing on aircraft.

They'll be named with letters of alphabet from A to Y (Z is reserverd for marking last ordnance release point). And they'll be overwritten - when you reach Y letter next markpoint will be named A.

As it was the only thing mentioned in changelog for this release for A-10C module I've tested how is KC-135 behaving now. And here goes a total dissapointment:( It doesn't look as fixed. It looks as totally broken. In previous version an issue was about the amount of fuel that tanker would give to player (who hosts the mission) before calling "transfer complete". Now any attempt to refuel ends instantly with first touch of refuelling boom. Tanker will after that immediately disconnect the boom, call "disconnect" and "transfer complete" and you can give up ro try again and end in the same scenario. Issue is confirmed by few guys who also noticed it when trying to refuel. It happens in different missions in multiplater and also in singleplayer. Anyone else can confirm that tankers are unusable?

It looks like your x52 "I" button is configured to work as clutch button. Go to joystick control panel find Clutch settings and uncheck "Enable Clutch Mode" checkbox.

To get a picture of what A-10 were doing you should read two books: - Warthog: Flying the A-10 in the Gulf War - A-10 over Kosovo You'll find there a lot of information about how A-10 were used and how it all looks from pilot perspective. Definitely a good reading and a lot of information about mission types for A-10 and about tactics. It wasn't always as well defined and planned as Skall has described, but anyway he has a good point.

Same here. What more curious - when i clicked cancel it anyway logged me in and show me that I can download just bought MI-8 module.

Could you share a tacview acmi file or a track from one of your routine flights? Just to get a picture of what to expect.

Download DCS World then you can get all modules you need (using keys from standalone products to activate) Your standalone products are not needed to run DCS World modules.

Exactly:thumbup:

Contratulations! You've just posted a very generic and universal answer to majority of questions asked on ED forum ;)

Ensure you're between 0 and 10 deg. of bank and between -5 and +5 deg. of pitch else AP won't engage in this mode. Also check if you have EAC on.

In your game installation folder find file: ..Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua In that file find and comment out ine thing: (render_purpose.GENERAL). After commenting it should look like below: function set_full_viewport_coverage(viewport) dedicated_viewport = {viewport.x, viewport.y, viewport.width, viewport.height} dedicated_viewport_arcade = dedicated_viewport purposes = {--render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW, render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always render_target_always = true end And don't forget to define where you have both MFCDs in you monitor setup file.

ATC is directing you to IAF (about 10 nm from runway threshold). There you could be able to intercept glideslope (if your altitude is about 3800 ft AGL). How to measure distance you've travelled? Just make an overhead markpoint (with MK button on UFC) when you get info from ATC. Then you can hook to this markpoint and you will have both heading and distance displayed on TAD.

One more thing. If you have an X52 you can make trimming more accurate. Instead of just binding keys to hat try go to Saitek's profile editor and map trimming to hat as advanced command. I have it binded like on below image: It works like a charm. When you push a hat for a short period - you'll get a single, very small change in trimmer setting. When you hold it longer, it will start to repeat sending keystrokes and you'll get larger change in trimmer.

I've noticed such behavoiur when I was experimenting with my Saitek. What I've found was that you have choice: - use game settings and defining pinkie as modifier, but witout loading any SST profile. - use SST profile but don't use pinkie s modifier in game settings. When i tried to mix these approaches pinkie just stopped working during gameplay. I didn't try to setup a new, clear SST profile and then go to game settings and then define pinkie as modifier. Maybe it's worth trying.

Just get DCS World, install it, then get A-10C module and install it. Enter your key from "old" A-10C if it won't recognize it automatically at first run.

Very good idea! We've talked about that in my squadron many times since release of Huey. And it would be definitely great if implemented in the future.

Totally agree! Thx ED for all you've done in DCS. About weekly updates - even bad information is better than lack of information.

Might be, but when i looked at SAM's radar via TGP, it's antenna was turning around. And i don't think SAM is able to point tracking radar at some point in space where I just happened to be at exact moment, without having any idea of my presence in that direction, and track/lock on me momentarily. It might happen for Buk with it's independent radars on launchers but for sure not for rest of mentioned SAMS.

A-10C RWR Indications or some SAMs search radars are gone Did anyone already noticed that in A-10C you wont get info on RWR about radars being nearby in search mode? It happens for Dog Ear, Buk, Kub, Tor and probably some others. Effect is that first thing you get on RWR is info that you've just started to be tracked by SAM. Also when you look in Tacview ACMI for that flight some radars doesn't have "bubbles" showing their range. So now we have a situation when we are "stealthy" painted by search radars, and when we get in tracking/locking range we have first information on RWR that we've just been tracked/locked. I'm not sure if it's problem with A-10C's RWR or radars themselves, but based on Tacview visualization it looks rather like something was broken in radars behavior in 1.2.4. There are also major changes in missilles behavior, but it's still under testing. Main question is : what's wrong with SAM radars in 1.2.4? During flights we're feeling like walking on minefield:doh:

I don't think that we need ads in cockpit during flights. It would be annoying. And about application itself - it depends on it's functionality. There is always something to add to make using of DCS World easier / more effective/ more fun. Tell us more about what you're going to implement and you will get some feedback for sure.