Gate-5

Schade. Mittlerweile gibt es so vieles was unfertig ist, dass ich etwas die freude an dem ganzen verliere. Viel zu viel in der pipeline und eine sehr unglückliche kommunikation. Von der roadmap halte ich demnach nicht gerade viel. Zumal das ganze dann noch in die stable version sollte, wo sich seit dezember nichts mehr getan hat.

Found a cockpit video on Youtube without music. Sound quality is not the best but I cannot hear any engines at all once canopy is closed. I imagine it comes quite close to what Victory205 described.

I'd preorder, you get 20$ off and can use it as soon as you have time for it without waiting for a sale.

What a crazy spot :pilotfly:

[FBV]1711019335636387[/FBV]

I'm having the same problem in the Viggen. Yesterday it worked after some time and a couple of reconnects, today it's not and the connection times out in under a minute. EDIT: I was now able to connect to the Aerobatics Online Public Mission server. Only 5 people connected, compared to 20+ on the other ones I tried.

BLUFOR Lonewolf Callsign: Spike Preferred Aircraft: A-10C, F15, Mi-8, Ka-50

Im currently using this for all campaign missions, so far it seems to work. Calculating speed often results in the same number for multiple legs, so I think its correct.

I did check the other ones, but I dont think these are related to the numbers given for each leg of the flight plan, or am I missing something? IMOH the grid system is kinda useless since we dont have a complete map with the grid. The top numbers in my screenshot seem to be the distance in km, but the lower one, I don't know. Flight time in minutes maybe? Whatever :D EDIT: I think I've got it now and 49/15 260° means "Fly 260° for 49km and be there 15min". Resulting speeds would be from 180kmh to 225kmh for the flightplan above, which is reasonable for the Mi8.

Can anyone explain to me what these numbers mean? The heading is clear to me but what about the 49/15?

Yes. I'm currently using the "w" key instead of my rudder pedals. After landing I areobrake until below 100 knots, then lower the nose and tap the key until stopped. I noticed the plane pulling to the side also on takeoff (crosswind?), duno if it is the same thing and if it is supposed to be that way.

Hi Crunchy I just built a new system and had exactly the same question. Check this for my solution: http://forums.eagle.ru/showthread.php?p=2517097#post2517097 For the backup I copied the whole "Saved Games->DCS.openbeta->Config->Input" folders, as thats where all your key assignments are stored. With the Renamer tool you can search and replace within file names, so its easy to rename all backup config files to match the new USB ports.

Thanks for you help guys. I figured out what the problem was. Since I have new USB ports the filenames didnt match. Now my solution.... I assigned some buttons in DCS, this created config files for joystick, throttle and pedals. From these files I figured out the new number (e.g. {86D33930-7120-11e5-8001-444553540000}. Then I used this tool: Renamer to batch replace the numbers in my backup configs to match the ones created by the new install of DCS. :thumbup: At least this works for backup and restore for the same version of DCS. For updates this probably might mess up some modules because of changes to the inputs.

I updated my system and had to wipe my windows isntall. In order not to go through the utterly painful process of setting up my controls for all modules again, I backed up my settings from the users "Saved Games" folder. After copying back, the problem is, that my controls are still assigned somehow, but the same for every device (see screenshot). This also happens when I buy a new module, instead of a blank config, I get a somehow correct but also messed up one to start with. Is there a way I can recover this?

I had the same problems with the immelmann because I didn't keep the G's up in the second half of the upwards loop. Now I end up above 210kmh when entering at something above 600kmh.

Ok I was using the wrong shortcut :doh:. The one that works is [RALT+\] for SPU-9 PTT on the cyclic stick. What doesnt work is "Communications Menu" under "Radio Communications" as stated in the manual . Furthermore it says"“РАДИО” (Radio) button – Activates radio in transmit mode. No function." for the button that has to be used now. :pilotfly:. Is [\] used for easy coms? Anyways, thanks for the help :thumbup: :thumbup:

As the title says. As soon as I take off I cannot open the comms meun again. It also disapers when I open it on the ground and then take off. I hope this has not been reported yet, but couldn't find anything when searching. log_and_track.zip

Having the same problem, heres my log. dcs.zip

Two wooden disks with a bolt and parquet floor gliders :thumbup:.

You might want to look up the Virgin Galactic Spaceship Two crash, Peter Siebold was ejectet out of the spaceship at above 45t feet and mach 1 and survived. http://www.latimes.com/business/la-fi-virgin-pilot-testimony-20150727-story.html

Well that was a no brainer... :D. And finally the day has come, where I can upgrade my PC without fearing it being old again when DCS 2.0 is here. But will StarCitizen run too when it comes out? .... :D:D:D

Some more details about powerplay: Newsletter #72

Against columns I usually take a set of FAB100 and go in low and fast, works quite nice. Other than that I often use S-32 rockets. A salvo of 4 can be sufficient for artillery or soft targets. Would be interesting to try, do you have some tables for such kind of deliveries?

Had the problem just now again on one of the STP servers. In the track I join a slot, turn on battery and fps go down, battery off, back to spectate and into the same slot again and its gone. Hope it helps, if you need some other information or there something I should try, just tell me and I'll do so the next time it happens. client-20150214-155841.trk

I experienced this bug in MP a couple of times too. The only thing I had to do was to go back to spectate and select the slot again. It always happened the first time when selecting the slot after joining the server. I'll try to provide a track the next time it happens.