Dejjvid

Until you get past gimbal limits. Then you will scream in despair and wonder why you didn't mark the enemy. ;)

The Seven-G project looks more and more like Duke Nukem, that's a pity. Could be awesome. Perhaps we have F/A-18C or the F-15C this year. But then again, when Wags give an estimate a big part of the community take it as a fact.. So i don't think he'll do that again.

Nothing wrong with the VRS team, except they develop for the wrong platform..

Regarding lase time. Default release WILL overshoot the target if you don't activate the laser. IF you are engaging a moving target you should activate the laser at minimum 15s depending on altitude. The most flexible way is to ignore auto lase and enable LATCH in TGP CTRL page. This way you enable the laser with a simple push on NWS and stop it with the next push. Very very convenient, and flexible.

Hey Trev, Why don't you just edit the default profile? It will apply to every GBU-10/12. It's much faster then creating a new custom profile. I can't even recall the last time I selected a station in the DSMS btw.

If you got trouble flying the Ka-50 you will loooove flying the Huey ;)

Omg. x64 is not a hype anymore. It's a standard. If you bought a computer the last 5 years you will have a x64 CPU already. Upgrade the OS and you're set. Welcome to the future :thumbup:

FFB issues is fixed with 1.2.3. Run the auto updater. Only bug that's annoying is the "crazy Shkval". Seems like it happen more frequently in the southern part of the map. Fixing this and the Ka-50 is "complete".

Unlinked ofc, only link them when I fly Ka-50 or single engine aircrafts.

Did they fix the EO timer? IIRC the degradation was not implemented before, or at least not noticeable. I've never had any problems at all with accuracy, but then again I only activate them before I plan to use them. Perhaps you are spooling up the Mavs too early?

I bet 1st 3rd party release is special for both the community and Belsimtek/ED. If I were producer I'd test, test, test and test again to make sure everything is working as intended with DCS World. ED will not only be responsible for its own income, now they have 3rd party companies that rely on EDs work. That is one hell of a responsibility.

ED has been silent before every big release so far. They only communicate if they are having issues, or strategic info. Don't you remember when a lot of us pushed F5 for a new beta of A-10C and suddenly we got a release instead?

I modified (added more units) Operation Kano 3, awesome mission! Only thing that could be improved is that friendly units start too close to the enemy, but otherwise we had a blast.

I need a 12-16 player mission with at least 4 Ka-50s. And at least 8 A-10C's. And I need it in 35min ;) Any suggestions?

Software firewall?

Sorry but you are wrong. You can NEVER slave your Mavericks to your TGP. You slave to your Sensor Point of Interest (SPI). It is crucial that you understand SPI and Sensor Of Interest (SOI). There is a ton of tutorials explaining SOI and SPI, I recommend you watch and read until you understand them both 100% before you continue. It will save you tons of frustration and you will be able to operate the A-10C much better. Edit: Regarding the lock. You can not lock the Maverick outside the launch range. The furthest out you can lock is ~10NM with Force Correlate mode, and only with the biggest Mavs. Otherwise you get lock around 7.5-5nm under normal conditions.

The net code does not handle packet loss very well, it feels like they've tweaked that part a bit. But I'd like to see a implementation like they have in most online games, the server should put you "on hold" and disregard any new packets until you are stable again. This way you will only freeze, not be kicked out. In the current state the server will close your session after a 0.3 sec timeout. You will never notice this when playing without tracing your packet loss rate, and this is why most of the posts about disconnects are made, blaming ED. When in fact it's their connections that should be blamed. The only way to correct this "problem" is increasing the timeout timer, but this might introduce some nasty stuff and might require a completely new net code.

Awesome tip c0ff, wonder if :1.2.4 works as well? ;) It's funny when people pre-purchase a game, get access to the BETA and then whine like they got a porked release version.

Never had any crashes in 1.2.3. The net code still doesn't like connections with packet loss though. Hope it is possible for the devs to tweak it so the server doesn't drop the session and only "pause" the client.

Thank you MadTommy, didn't have a clue about the coalition requirement.. :thumbup:

I like too AAR with a slight nose heavy trim. This is like riding a bicycle once you've learned it it's really easy. Practice tight formation flying with friends when you fly towards mission areas. Try to place your wingmens wingtip 2ft from your canopy and keep it there. Practice turns, descents, change of speeds and learn to anticipate the other aircrafts movements. When you feel pretty stable try AAR again.

Ok, why can't the sensor track upside down or with 90 degree bank?

When i do pop up attacks i very often fire inverted, or banking 90 degrees. You have to pull negative G's in order to hit your own Mav.. :pilotfly:

What the Network Speed settings actually do is at least for me a mystery. But i do know that there are values specified in config files you can change. But tests done on 1.2.2 did not show any difference. So if the net code change your MTU, update frequency or reducing overhead is not known to me. Anyway, Masterarms only use LAN, and it works for us on every "normal" mission. If we soak the map with units and try to re create WWIII we do get warping, and we probably need a Dedicated server in order to play those massive missions.

Repair is in the Start menu Eagle Dynamics>DCS World> Repair