71st_AH Rob

BLUFF: Yes Install to the appropriate saved games directory exactly as you would have previously to the games root directory. For example your mods should go in a folder "C:\Users\Rob\Saved Games\DCS.openbeta\_Mods" and the "C:\Users\Rob\Saved Games\DCS.openbeta" folder should also have your JGSME application, configuration and help files and the JSON. you can copy your previous mod folder over or the entire install but then you need to go into the JGSME.Confg file and edit the path to look like: [JSGME DETAILS] FullPath=C:\Users\Rob\Saved Games\DCS.openbeta\JSGME.exe

On the Normandy and Nevada maps, if you zoom out in the editor as far as you can the area is ~1500 x 800 nm. If you place a FARP at any of the extreme corners you can spawn a helicopter and fly across the map. In the Caucasus map if you do that in the extreme corners your FARP will work , but more importantly at the extreme edges of the map at the Black Sea you can spawn ships including Aircraft Carriers. If you try to spawn an Aircraft Carrier in the Pacific Ocean on the Nevada Map it won't work. FARPs and ground vehs work fine.

Looking good, can't wait to see it patrolling the Black Sea

VoiceAttack will work in MP but you need to set up a profile for each game and for each module in DCS, VIACOM is a great plug in for VA that makes it work out of the box. Hollywood has done all of the hard work of making a profile for you. It works in single player in the free version but you need the paid version to use it in multiplayer. Some people want to use it to activate a/c commands, I use it only for those actions that you would give spoken commands over the radio for. It is particularly useful for speaking to the tower on approach, AWACS and JTAC when you really don't want to take your hands off of the HOTAS and you don't want to go searching for the correct F key or try to remember what it is because you can't read it on the screen. I recommend it, I use it every flight in MP.

Sadly this bug, although widespread and common, does appear to be inconsistent. I fly the Sabre regularly and there is no obvious trigger, nor common circumstance. It happens in multiplayer and single player, on all servers, sometimes immediately and sometimes after many hours. In about 100 hours it may have happened to me twice and then the following week it happens twice in a day. This will be hard to track down

Refresh my memory, how may days, or hours if you prefer, did the air war over Georgia last? It is precisely because it has half the land mass of Nevada map (and most likely a tenth the structures) that this is going to be a great map. Particularly with the new carrier tech to be introduced to DCS world and a few high fidelity carriers announced. I think it would be a perfect first attempt at a map being mostly ocean development should go fast since there is little terrain to model and few structures compared to other maps. Also with the few trees and structures, and mostly ocean I would anticipate that performance will be good.

Not only no burst but no effect either. No muzzle flash either but you can hear the 88 fire and it will track targets.

Thanks, I'll have a look at it this weekend!

The 88 doesn't work again since the last update in multiplayer anyway, at least you can see it and the animations work as well as the sound of firing, but there is no muzzle flash or shell burst and you can fly circles around it at any altitude without fear of taking damage.

+1

How?

+1 Also a mid-44 Spitfire XIV and we could use a couple of FLYABLE twin engine med bombers like a B-25 or 26, a Mosquito and a German twin engine, a Bf-110 or a Ju-88 maybe. Never mind the four engine bombers, we need a map for them first as much as I want them.

This is a bug when playing the generated missions in multiplayer with some aircraft types. The generator assigns custom frequencies to the players a/c but not to the other a/c in the flight. For some cases opening and saving the mission in the editor seems to reset the remaining a/c from their default frequencies to the new custom ones. For other a/c types it is better to manually set all the frequencies and save the mission prior to playing in multiplayer.

The last time I checked only the red coalition could use EWR for GCI. Both coalition's could use AWACS.

And so will the server. All three will need to be installed in the same directory, if the server has them in a different directory than the clients you still will not see them.

I fly the Sabre in 4K and find now in 2.5 that I can spot bogeys as far out as 20Km in perfect conditions when they are above the horizon. Below the horizon is a different story and the addition of light glinting off of the canopy and polished metal would significantly add to acquisition of targets. At the merge, it is now significantly easier and I think more realistic to maintain visual contact with bandits even without the HUD cues and other aids found on more modern aircraft or the use of spotting aids like icons or scaling, although I am not opposed to either since even a 4k monitor only simulates a poor vision in the real world. In short, for WVR combat the Sabre and Mig-15 are the most difficult since merge speeds are much higher and vertical changes much greater than WWII a/c and you don't have the technical aids of third and fourth generation fighters to aid in target acquisition. There are plenty of kills scored on Korea 1952! server even though many are playing in 4k like I do.

The single black bands were introduced before D-Day, shortly after the Mustang was introduced in the ETO. Before the a/c was clear for operations and units were still doing conversion TRG (334ths springs to mind) there were several unfortunate misidentification incidents where P-47 pilots confuse them for Bf-109s much like the introduction of the P-47 and the solution was similar. To avoid confusion with the Fw-190 they painted ID bands around the cowling, tail and wing roots in white paint. I can't think of an example I've seen of a white band on the nose of a Mustang, most FGs had various bright colours id'ing them before the Mustang was introduced. When the Mustang went to the natural metal finish the white bands on the wing roots and tail didn't show up as well so they switched to black. I don't have the dates handy but the tail band disappeared on the Mustang when the FG s adopted the coloured rudders/tails and the wing root bands disappeared about the time the invasion stripes appear. I can't think of an example of one that I've seen painted on after D-Day but you might find some lingering after.

The server and client must have the same version of the range objects loaded the same way. I did find that I had a similar problem with loading the objects on my server, redid it and it worked fine in MP afterwards.

They are Joy_1 and Joy_6 I think

I think that the fundamental problem is that you made the same assumption I did that the lower the priority number the higher priority the target. I had assumed that the he #1 priority target would be the one that had a priority of 1 in the target list, however I believe I read last week that the highest number priority in the target list is your #1 priority target. I read through all 67 pages of this thread looking for an answer to a problem I was having and was surprised to see it, I should have bookmarked it. Your formula above would seem to corroborate that post though.

Nice! Looking forward to seeing it.

If you cant see it, check the file extension and make sure it is still .miz and not something else. This happened to me once and windows had changed it to .zip or txt can't remember

Link is broken

Just in case you were not tracking, in DCS 2.5 OB Spitifre will cause the DCS to drop out of multiplayer to the main screen if it takes damage at the moment and if that player is the host of course everyone is disconnected. Also AAA guns are only visible to the host in a multiplayer game right now. Maybe it will be corrected with a hotfix tomorrow. This is just to stop people wondering if they installed it right, it is a DCS problem not you or the mission builder.

^This already exists