Leto

Hmm... shouldn't act like that. Please try ground power instead of APU and check if the same thing happens.

should be like this: You can request rearm/refuel when - canopy open, engines not running without further settings - when engines running/canopy closed: set the rotary selector dial on intercom control panel to "INT" (see page 130/131 and 153/154 in A-10 manual) but there seems to be a bug where you can request rearm/refuel eventhough engines running+canopy closed+no interphone selected. http://forums.eagle.ru/showthread.php?p=1578124#post1578124 Rearm/Refuel you can either request by VHF AM F8 menu or on screen display (german keyboard L-ALT+Ä). Repair only via F8 menu and shut down engines. If you shut down your engines you can either request ground power via F8 menu or use your APU + APU generator so your systems stay powered. Resetting DSMS: chose one of the menu items on the bottom of your left MFCD. For example "STAT". Press "STAT" for about 2 seconds and a menu with all possible menu items will be shown. You'll find "LOAD" on the right side. Press OSB for "LOAD" and then "STAT" again. Now you changed "STAT" to "LOAD". Press the "LOAD" button on the bottom and the "LOAD MENU" will show. On the left side you find "DSMS Load"... voilà

oh yes! That would really be nice. My personal wishlist for DCSATC: - TARS integration - Airport mode (control zone plus proximity) - editable control zones around airports so we could create our own control zones - integration of JaBoG32 visual approach charts info http://www.virtual-jabog32.de/index.php?section=downloads&subcat=37&file=1214

@Echo: reproduced your test flights in 1.2.0 6192 like this: loaded your track, paused, took over control. So all parameters should be the same. First flight clean after 6min: 317 IAS Second Flight with loadout after 6min: 284 IAS (ball centered by SAS) In your clean configuration there is still around 800kg of GAU ammunition. Weight and/or drag seem to have been changed. And for me a delta of 33kts with the loadout is more believable than 8kts in 1.2.0 Could you do another testflight with same configuration @ altitude 20000ft? And also some tests clean with different weight (100% fuel compared to 20%)

Exactly! And after a long day with the hog performing attack runs by the book, following exit and entry procedures, proper ground handling and so on, who doesn't love to jump into the stang and go crazy :D

http://forums.eagle.ru/showpost.php?p=1570344&postcount=3

woohoo! 6192 doubled the framerate for me. Small stutters and flickering clouds detected, but for now: thx ED! :thumbup:

Answer here

jep... I second that... despite all these problems can sometimes be quite annoying ... keep up your good work! :thumbup:

That's my usual setup: Nvidia control panel AA/AF -> application controlled MSAA 4x TSAA off, clutter & trees minimum.... microstutters en masse and our machine specs a nearly the same

Done. Clutter/Bushes/Trees all to the left (minimum settings) Disabled AA/AF in NVIDIA control panel and AA in DCS. Fired up first A10 instant mission... 40 fps (I got around 60 with 1.2.0 and AA/AF on in this mission)... positive effect: no microstutter Tried forcing AA only, AF only and both in control panel. Slightly decreased fps (around 35 or with higher AA settings 30) but due to microstutter it's not playable Set back to application controlled AA/AF with 4x in DCS results in around 30-35 fps. But due to microstutter it's not playable Only way for me to get rid of microstutters is to disable AA&AF in NVIDIA control panel. Each value I set forced or application controled leads back to microstutter.

rightCTRL+PAUSE

fps slightly better but not as good as 1.2.0 mouse cursor still annoying still severe micro stutters... sometimes 3-4 times in one second loading time better, but not as fast as 1.2.0 still big difference between lights on/lights off on aircraft (10-15 fps) new apu sound is no improvement...on the contrary Gau impact explosions look "comic" style... I would appreciate a menu option for the alleged eye-candy on explosions like Gau/CBU's... they cause a severe impact on fps and should be possible to turn on/off

Amount and draw distance / visibility of houses, structures etc in villages and cities

It's in feet from the centre of the lead object. Example: you want a F-16 fly near KC-135 you set the F-16 to follow/escort KC-135 with x = -300 y = 200 z = -400 F-16 will be 300 feet behind 200 feet higher 400 feet on the left add a F-18 x = 500 y = -150 z = 600 F-18 will be 500 feet in front 150 feet lower 600 feet to the right of KC-135

thx for the quick answer. AI on MP would be a blast :D

@Druid: these new commands work AI on AI only? Tried to set one F18 to "follow" and one F18 to "escort" my self piloted A10. On mission start the two F18 just fly circles. When I shift "my" A10 to KI it works.

I am sure it is on their watchlist already. Druid (ED Tester) postet this picture so at least he is aware :smilewink:

Confirm. Exhaust while rocket motor is burning is kind of turquoise now. Contrails also look a wee bit weird:

It feels like power/drag/weight/lift ratio has changed. In critical flight situations (high AoA/very slow) behaviour is more sluggish now. Yesterday while testing I lost the right elevator and rudder. The impact on flight behaviour was more severe than I ever noticed before what felt right. I like it :thumbup:

first A10 instant mission: -Loading times of mission is a lot longer now -once in the mission before I hit "fly" game stutters (TrackIR view) and after around 10 seconds it is ok -once I hit fly and mission begins I have 10 seconds of 0-1 fps, then around 40 fps which seems good but I got micro stutters every couple of seconds

1.2.1 6055 released Autoupdater just brought me 1.2.1 6055 after I deleted my user/savedgames/dcs folder. Most likely that is not necessary to get the update, but for DCS is checking just once a day automatically you might want to check manually for an update.

Unfortunately it's still killing my fps from 50 to 7 in F2 view

Sounds good... staying tuned :thumbup:

Confirm... highly annoying! Could that also be responsible for fps drop in 1.2.1? With all previous patches I didn't experience such an impact on framerate :cry: