sthompson

Thank you for the advice Stone Sky. I deleted the campaign and then did a full repair of DCS opebeta using the slow mode and deleting extra files. Then I reinstalled the campaign. This did solve the problem and I was able to fly the mission. However, I found that many of the mission messages did not include an audible voice prompt, even though I could read them on the screen. I also found that they occurred at random times and in the wrong order. For example, after getting a message to RTB I did just that, but after I was already on the ground and taxiing I was told to land. Then my "own" pilot voice started complaining about the high G's. I also got repeated messages about flying above the 2500 ft limit even though I wasn't doing that. On the other hand, I sometimes broke the hard deck and there were no complaints. I imagine there are some issues with the triggers. One other piece of feedback for future revisions if any. I'm not very familiar with the aerobatic maneuvers I was supposed to be doing. It would be helpful if you could include some resources or links to resources to make it clearer what I'm supposed to be doing.

Could be related to issues already known to the Community developers. See

I bought the campaign some time ago but never tried it until yesterday. I found that when I press the "Start" button from the mission briefing the mission starts to load but then stops loading about 70% of the way through the "Sim PostStart" stage. DCS stops responding and CPU/Memory/Disk usage goes very low (sometimes to zero). The first time this happened I thought that the mission was just loading slowly so I went away to do something else for a while. When I came back more than an hour later there was no progress. This is using the latest openbeta DCS version. I've tried both with and without MT support with the same results.

Thanks for the quick fix. I flew Missions 7-10 yesterday and today to finish the campaign. They worked perfectly. The campaign is very well done!

Also improved performance.

I'm not a real life pilot but I've flown as a passenger in plenty of turbulence. A lot of comments are about what you "feel" in turbulence. I don't see how you can really model it in DCS since the key sensations are all about G forces. In a passenger jet with severe turbulence you might also hear things rattling around in the overhead bins. But mostly it's about the lateral and vertical accelerations. Visually, at altitude, there really isn't much to see unless you are near another plane, or your head is bobbing around. So what exactly would better turbulence modeling be like given that we can't feel G forces?

I'm enjoying the campaign but am unable to get a Mission Complete on Mission 7 (Battle of Qeshm). Peeking into the mission file it appears that there needs to be a hit on the Oliver Hazzard Perry class frigate BNS Bandar Lengeh. I'm only given air to air weapons so this must come from the flight of Fencers who target that ship. They launch their X-31A anti-ship missiles from below 700 ft ASL. The missiles fall into the sea and are destroyed soon after launch (according to Tacview) and never get close to their target. So the mission goal is never met. Is this perhaps a DCS bug? Is there a workaround (other than skipping the mission)?

You obviously haven't flown the I-16.

I've not often flown missions where I needed to use the JTAC dialogs until recently. I've found (at least in the JF-17) that JTAC does not work at all (either using VAICOM or the communications menu) if VAICOM has been run, even if VAICOM is not currently running. To be clear, I can issue a "playtime" command via the communications menu but nothing happens. Doing a DCS repair (to take out the VAICOM modifications to lua code) solves the problem. All of this is on the current Openbeta using the latest community release of VAICOM

Kneeboard Builder's options for adjusting the position and size of the kneeboard have been broken ever since DCS introduced that functionality into DCS itself.

That's not so clear. For now multithreading is an option under Openbeta, and you can run Openbeta ignoring the MT stuff. That suggests they could port over a number of the OB features (including the Normandy map) even while not including multithreading support. On the other hand, the performance improvements for me using MT are so great that I will definitely be staying on OB for now.

That location is outside the high detail area of the map. More likely to be present on the Channel Map, but I've never checked.

The new map is vastly larger than the old one. It's more than a "refresh." And you get all of that for free if you own the old one. They are only charging for a lot of really excellent new eye candy detail. It's a bargain.

@Reflected posted a nice video about Normandy 2.0 that pointed out that it would be basically impossible to port his existing DLC campaigns for the Channel map to an enhanced Normandy map. He would have to start over from nothing on the mission programming. So keeping the Channel map is about more than just ED's sales of the Channel map itself.

You need to update your Openbeta installation. Normandy 2.0 is apparently part of the update if you already have Normandy 1.0 installed. It isn't installed seprately and does not appear separately in the module manager. Purchasing Normandy 2.0 appears to just unlock the hi-res features. (All of this might be different for Steam users.) That's correct, but if you have done the DCS update then Normandy is now the high res version, and purchasing Normandy 2.0 unlocks the hi-res features.

That was my situation. I updated DCS, which took quite a while, then purchased Normandy 2.0 (ignoring the warning that I already owned it). Then upon restarting DCS I had it. No further download was needed, and I didn't have to do anything with the module manager. So apparently the high res version gets downloaded as part of the update even if you haven't bought it.

Good question. It's been a mystery to me why DCS cannot at least let you define defaults for stick, throttle, rudder axes, which would then be overridden if defined in a specific module. You can save out control settings from one module and then read them in on another module. But this can lead to some inconsistencies. For example, if you copy settings from module A to module B but module B supports some keybinds that are not supported by A then they might end up not being available in B either. At least that's my recollection about what happens when I experimented with this years ago.

Could be a time zone issue. Google gives the time of sunrise on that date as 5:49 AM local time in Paris, but that's GMT+2. The map may use GMT.

Even though the FAQ says ... Campaigns such as those from Reflected Simulations have been updated and should be working at release. Please watch his video on this here. Apparently no one is checking before release.

The Normandy 2 FAQ includes the question "How big is DCS: Normandy 2.0 compared to the DCS: Normandy 1944 map?" Could someone answer this question as it pertains to disk space? For example, I'd like to know how much more disk space I need for Normandy 1 1944 with the new enhancements compared to the old Normandy map, and same question for Normandy 2.0. My SSD is close to full.

Did you do the FINISH step? What happens when you push the "TEST" button. (Be sure to wait until it completes. It doesn't put anything in the log right away.) Do you have extensions enabled? If all else fails you might want to go to the reset tab and reset your database. (You may need to run FINISH again afterwards.)

Text formatting in Chuck's guide is definitely a bit weird. This is most noticeable when you do a text search and find that search hits occur in strange places. There seems to be a lot of hidden text. To see this further, try opening the Guide in Acrobat Reader, then copy some of his text and then do a "paste special" into a blank Word document. Select "unformatted text" as the special method to see what I mean. Each word appear multiple times. Opening the document properties for the Spitfire guide document in Acrobat Reader and then looking at document properties it appears that it was created using PDF-Xchange. Possibly if you use that software to export to PNG you will have better luck. You might also have better luck if you capture an onscreen image and paste that into a Word document (then Save As pdf) rather than trying to import Chuck's Guide itself directly. I've used that method for some of my custom kneeboards.

I tried it out for the first time yesterday. If you slew TDC over a contact while in RWS mode and then press and hold the TDC switch the radar scan changes to a narrow beam directed at that contact for as long as you hold the switch depressed. When you release the switch you will find the contact bugged in SAM mode. It isn't clear to me what advantage there is to doing this. I found some F-16 documentation that suggests that the narrow scan lets the radar build a more accurate track file. But I can't verify that this is the case for the JF-17 simulated implementation.

In the current version, page 130, HOTAS throttle controls, the column headings for AA master mode don't make any sense. That is, there are two groups of columns both labelled for INTC mode. Furthermore, four of the column headings are labelled the same thing. I think these are probably supposed to be the same column headings as on the previous page (i.e. for HOTAS stick controls).

As documented in the readme file.