Winston 60

I wouldn't think so. It's most likely the lack of proper Dx11 video that is causing your issues.

Are you releasing the 97's at 10,000ft? That's way too high... the wind will blow them away and the dispersal from that altitude will make them ineffective. Start from 10,000ft altitude and get close enough to your targets to make a steep dive to get the CCIP pipper visible and on target. Don't forget to compensate for vehicle movement if they are not stationary. Drop when lower than 3,000 ft... then quickly get out of Dodge!

You could check with the manufacturer to see if this particular laptop has a slot or socket for a dedicated DirectX11 DCS suitable video card with at least 2gb VRAM. If it does have this socket or slot, you can install and configure a video card. However you most likely will find that it does not because this model is listed as a "business computer".

Your laptop is below minimum spec for DCS. You must consider that an intel integrated graphics solution is not really a good choice for graphically demanding games. Some part of your 4gb of system RAM (also below the 8gb minimum) is being used by the intel graphics leaving you with less than 4gb of system RAM. If you must use a laptop to game, get one with 8 to 16gb of RAM and a decent dedicated video card with 2gb or more of VRAM or stay with the old 1.2 version of DCS.

^ This ^ It seems the ASUS P-Series P2540UA-AB51 is a business computer with an intel integrated graphics solution. Some part of your 8gb of system RAM has to be dedicated to video RAM which now makes your system RAM less than the minimum spec for DCS. Integrated graphics solutions are not usually a good choice for extreme gaming. If you must use a laptop to play games, get one with a decent dedicated video card with 2gb VRAM or more.

but now with this... gunners don't shoot, right?

Is there any reason to get this if I'm now using your previous v1.2a and I use it in the release version 1.5.6 only?

A good DCS ECM pod discussion is going on here: https://forums.eagle.ru/showthread.php?t=187810

I've never locked anything, helo or plane, going more than around 150km/h. This means a helo going less than top speed or hovering, or a plane close to landing.

The A-10A can lock slow moving targets with it's Mav's. Slow or hovering Helo's and some planes on short final are very susceptible. Can't lock onto fast moving aircraft.

I think you're looking at this backwards. ED isn't supporting open alpha and open beta users, rather the open alpha and open beta users are supporting ED by providing pre-release input, suggestions and bug reports. It's either that or throw out release versions full of bugs and then we get frustrated and wonder why so many bugs exist and how they can call it a stable version.

Jaznit, I don't use ver 2.0, but here are some ideas based on the 1.5 mission builder. Perhaps they are the same or close? I'm sure some 2.0 builders will see this and chime in. * You may only use countries and their aircraft that you pre-selected when beginning a new mission. The country selection box should be the first thing that presents itself when you create a new mission. You can move countries in and out of the Red and Blue sides and also into the Neutral area. * Bullseye is especially useful for AWACS callouts as some bogey info is given relative to bullseye. * On your ceiling barrier, you can use the condition: "units altitude higher than" to trigger an event or a message/sound file that you are above the mission altitude. I hope that gets the ball rolling with some ideas for you.

You can't. Don't worry about it... a mod may see it and delete it or it will eventually drop away into older pages. The main thing is I now see your questions posted in the correct place, hopefully people will reply to your topic there, and can still have a look at your mission here.

Better if you posted mission building questions in the "Mission Builders Corner" topic above. This topic is for mission builders to post their completed missions and campaigns. Plus, you'll probably get more attention to your questions if you post in the above topic. :thumbup: Or break your post into two parts, post the mission here (like you did) and ask for critiques while posting your questions in "Mission Builders Corner". Just trying to help, mate. - Without order there is chaos, without structure there is instability

Will this work fully and properly when flown by the AI?

Hey Sport, why the snide remarks? The guy asked a simple question asking for information. In fact, most of the posts you make here are derogatory in nature. Do you ever contribute anything positive to this community? Look at SkateZilla's post and see how you could possibly have done better. Maybe you can turn over a new leaf today and start replying with a little compassion to your fellow forum mates. We are not your enemies.

Good tip! :thumbup:

Outstanding work! It's great that you are maintaining these great cockpit mods! Rep added.

Looks great! I guess that answers my question about being able to get proper nose bort numbers on this. For so many years the original DCS Mig-23 could not fully display any 2 digit nose bort except 11.

Ripple quantity and interval settings are for bombs, Salvo mode is for vikhr missiles. There's no indicator, it defaults to fire one missile and alternates firing from one wing then the other. Pressing Salvo mode keys/button changes to firing two missiles in rapid succession. Since there's no indicator showing that you have switched to Salvo, you need to remember that to go back to firing a single vikhr you have to press the salvo keys/button once again. Flashlight does not work. Pressing Receive Mode keys/button toggles between the types/brevity of comms you will receive from ATC and AWACS. Each keypress/buttonpress will display a window in the upper or center right of the screen to tell you what mode you're in.

Thanks to SinusoidDelta, your fix returned the backup compass and cut out a bit of the glare. Thanks to Knock-Knock, your fix removed most of the remaining glare on the cockpit glass. Nice going guys! :thumbup:

Only on "kill the train" missions or, if you have 10 clients, you'll have the same train in 10 different places as each player enters the mission at slightly different times. :huh:

This worked great! We all saw the train in the same place using this technique. Many thanks!

Thanks for the info Pikey. :thumbup: I'll try making sure all clients are in their cockpits before un-pausing the server to see if we can get a better sync.

I can verify that the Su-27 backup compass is no longer there, now replaced by some weird looking graphic that displays like an artificial horizon. I don't have the blocky like splotches on my Su-33 though, did you try a repair? The new reflection/opaqueness of the instrument glass is being discussed here if you want to add your observations: https://forums.eagle.ru/showthread.php?t=187472