fjacobsen

They missed the boat again it seems. The latest file dates are from 24-04-2019 (the day the previous patch was released). Sometines I wonder how much communication there is between ED and Razbam.

*Small adjustments to thrust and drag models

RIO does not set the individual targets, the AWG-9 weapon system automatically prioritise targets. The RIO can assign a target as mandatory or exclude a target. For multiple AIM-54 launches, stay in TWS mode. Watch the TID closely ! When a group of enemy aircraft appears, they will show up as only one target when far away. Only when they get closer will the AWG-9 system be able to see them as seperate targets and a priority number will be assigned to each detected unit. This number is replaced by Time to impact when a missile is launched against it. The number will start to blink once the AIM-54 goes from semi active to active. The distance where the AWG-9 weapon system can see them as seperate units, depends on the groups formation spacing, target size and some other factors. A group of 6 TU-95 with a formation spacing of ~1000 ft will start to show up as seperate targets at around 25nm. Going into STT mode means that the radar only focuses on one single target and thus all fired missiles will go for that.

It´s very complex, but manageable. Watch all those great Youtube videos.

I'm pretty sure that You cannot lock multiple targets. Locking the radar means that it concentrates on one single target and forgets about the rest. I think the AIM-54's can be launched without a lock, but are assigned their individual targets based on the priority number and target position is haded over via datalink until their own radar goes active.

You must also set the Airbase to be on Your side (Red or Blue) Click on the Airbase in the mission builder and info about it will be shown on the right side of the map. Select what side it belongs to.

I have now send a support ticket to ED - let´s see what they have to say.

I just wonder why none of the developers chime in here to tell whats going on. I thought this was a project done for professional use and made available for the public. I doubt professional would find it Ok not to be properly finished. Seems this is another DCS abandonware.

+1

To set the PC: Push the VTOL button on the left side (VTOL, NAV, AG). On the ODU You can now set NRAS and PC. NRAS is the speed at which You rotate the nozzles downwards during a short take off, and is dependend on aircraft weight. It can be found in Chucks guide, page 71: https://www.mudspike.com/wp-content/uploads/2018/12/DCS-AV-8B-Harrier-Guide.pdf Nozzles are initially set to 10°. With an aircraft weight of around 30.000 Lbs NRAS should be set to 98 kts. Once You start accelerating, the airspeed indicator on the HUD will become boxed at 98 kts, telling You to rotate the nozzles down to 55° (55° is set via the Nozzle stop lever). The PC caret is normally set to 14 °, but since the witch hat is depressed 8° below the horizon, the PC carets will appear at the 6° pitch ladder (1° above the 5° pitch ladder). Remember that for a vertical take off, the nozzles has to be rotatet to 82°. Once You make a vertical take off, Yu will put the witch hat on the horizon line i.e 82° + 8° = 90° - thats perpendicular to the ground. Max AOA is 15°, above that You loose pitch authority, thus the PC is set to 14° (1° below max AOA). That means that You should never pitch the witch hat above the PC at speeds in the transistion range (the sped range where You transistion from hover to wingborne flight).

For taxi You must turn off front wheel brakes by moving the lever to the left of the gunsight controls to the horisontal position (pointing left). Use no more than 10.000 RPM for thrust to get going. From there on it´s just about practicing using thrust, rudderpedals an brake lever.

It´s an error in the training mission - these switches should not be turned on and are only used in emergencies.

Various switch and knob animations Many knobs can be turned indefinatly around. Once they reach the fully open/closed position, then just reset back to the opposit. This is the case with the Oxygen valve, and light reostats on the righthand side panel, and most probably also with other knobs. The switches on the righthand side behind the glass cover, can be switched with the cover closed. Generally it´s hard to see the switch positions due to the very dark cockpit.

Iss the oxygen system inop ? I never see the flow indicator start til "blink". Also turning the Oxygen valve - You can turn it in each direction indefinatly, seems to opne, close, open close.... etc..

You need to create an account to get in there. I´m rather new with Discord too, but most "gamers" seems to use this for both comms and chat. As a former (and to a degree current) FSX/P3D developer, I have seen this trend for some years now. Developers being online in a direct chat room where they can do direct contact with the users. Personally I don´t like that, cause I rather want to spend my time down into the coding, rather by being disturbed by all kind of input - but in this regards I seems to be old fashioned. I also rather would like them to be active in this forum, where all DCS related stuff is collected, but maybe they don´t feel that it works for them. I still think they should make some weekly excerpts from thei online conversations here, inorder to communicate what they are doing and planning. My feeling was (and to some degree still is) - that the M2000C and AV-8B is at a standstill, and too little effort has been put in yo make any measurable progress.

Read here (I posted this further up this thread, but slightly more detailed here): I'm not very happy about the communication here in this forum, but I found that the Razbam developers actually are quite active on Discord - why this is so I don't know. Razbam_Tobbe seems to be the new guy brought in to further development of the AV-8B, so hopes to see this module being enhanced are higher on my end. Discord link: https://discordapp.com/channels/536389125276827660/544216278735257611 For those interested in the M2000C development, where Zeus67 is active look here: https://discordapp.com/channels/536389125276827660/544216334045544448

I got in touch with the coder from Razbam yesterday and he confirmed that a PC setting of 14 should set the Pitch carets at 6° and that this has been fixed for the next update.

The description of PC and Witch hat use is to prevent exceeding an AOA of 15° in level flight during take off. Level flight is, as we know, when the Velocity vector is at the 0° (Horizon line) of the pitch ladder. When this happens You will see that the Witch hat will be at 6° (just a tad above the 5° pitch ladder). From the Pocket guide: By default, Pitch Carets (PC) are set at 14 for all takeoffs. This places the pitch carets at 6o elevation with respect to the horizon bars in VSTOL Master Mode. This position indicates the desired post-takeoff placement of the Depressed Attitude Symbol (or Witch Hat). This takeoff attitude is the level equivalent of 14o AOA. Further from the Pocket guide: Accelerating Transition (AT) Accelerating Transition is the term used to describe transition from jetborne/semi-jetborne flight to wingborne flight. The AT begins when the aircraft is clear of ground effect and at an altitude sufficient to avoid obstacles and introduction of FOD onto the landing surface. WARNING During AT, AOA must not exceed 15°. Over-rotation or high rotational rates may result in the AOA rising uncontrollably even with stick full forward. Uncontrollable pitch ups are most likely to occur at extreme aft CG loadings and/or with the wing flaps deflected more than 25°. 1. Throttle.......FULL 2. Attitude.......SET WITCH HAT AT THE PITCH CARETS Continue to maintain wings level and vane centered. 3. Nozzles........GRADUALLY ROTATE THE NOZZLES AFT. Maintain nozzle angle of 25° or greater while in STOL flaps Nozzle rotation should enable the aircraft to maintain a slight climb. Remember that for vertical take off and landing, the Nozzles are set to 82°, thats 8° from straight down (90°) - which the Wich hat indicates. So for 90° thrust vector You must raise the nose inorder to align the Witch hat with the horizon line - thats 82+8 = 90°. Max AOA is 15°, exceeding this might cause You to loose control. With the Wich hat on the horizon line and moving forward with the Velocity vector also on the horizon line gives You an AOA of 8°. The Pitch carets now indicate the furthest You might point Your nose up in level flight safely -which is 6° nose up, so 8° AOA becomes 8+6 = 14° AOA . I´m not sure when You would want to set a different PC, but could be related to different CG of the aircraft, maybe with certain ordenance configurations or assymetric load - maybe some with knowledge ragarding this could chime in.

I see with todays hotfix that NRAS and PC now can be set via the ODU. But shouldn´t a PC setting of 14 not equal 6° on the pitch ladder ? Right Now a setting of 14 equals 14° on the pitch ladder. The PC is meant to ensure that You do not get past 15° AOA, thus the PC is set to 14°, but this equals this: Setting PC to 14 will cause the PC indicator to be set to 6° on the pitch ladder. Keeping the Witch hat aligned with the PC and the Velocity vector on the 0° pitch ladder gives an AOA of 14°. This is how I think it should work.

I hope some one from ED will chime in and give a more thoroughly explanation of what to expect. I added 8 GB more RAM recentyl to bring me to 16GB (the max my motherboard supports). It has helped alot, specifically for the Persion gulf map. But how to best use Your resources seems to be a mystery. No real gains to proper DCS memory control seems to have been added and feedback from ED is very spuriuos to non existant. Instead of adding more modules and features, I would rather like to see some fixes to allready notified and/or affirmed bugs, as well as a consolidating update to everything included. My feeling is that rather than nearing a real stable release version, we tend to move into an unfinished beta/alpha version, bringing in alot of unfinished content. Also ED should start whipping those 3rd party addon developer who doesn´t bring forward the state of their unfinished modules, and stop asking them to start projects that come in the way of the projects they allready got paid for in early access.

I just PM'd him - if he recieves PM's. Seriuosly - this tend to be amateurish to say the least - get Your acts together RAZBAM and start focus on what has been started - we actually paid real money for it !!

DCS itself will not move it into the pagefile. It will move the data into RAM and when thats full windows OS will start moving it into the page file, because the pagefile is the extension of the RAM. As the stuff in RAM is cleared, the content in the pagefile is then moved into RAM. I guess that the files from the Pre-load are kind of compressed when read from the DCS file folders and then unpacked into firstly RAM and then into the page file when RAM has ben exhausted. The sixe of the Pre-load area means that more data is loaded into RAM and possible page file. If You only have a small amount of RAM, then it makes little point of having a high pre-load radius, cause data will only que up in the page file. Having lot´s of RAM and a a high pre-load radius will mean that data is much quicker available for the sim. But things arent static, cause the amount of data within the set pre-load radius are dependent on the amount of objects (especially AI units). With 16GB or more I guess setting Pre-load radius to 15000 is fine for most non complex missions.

I did put in renewed hope that things would change when they hired =DECOY= to moderate this forum and post updates on progress. But now it seems we are back at point zero, with little feedback from Razbam. Please enlight us here in the official DCS support forum what´s going on. Errors do happen, but here it seems too common to just be errors. It´s time for Razbam to show that they actually do care about their paying customers - EA or not, this has become a real farce.

Then better not release any changelog if they aren´t certain that the mentioned fixes are in - it only adds to the confusion. How about hotfixes ? - now we need to wait another two weeks before seeing those meager updates being rolled out.

Yep - and NRAS and PC can still not be set on the ODU - neither on OB or Stable - so what where the mentioned fixes about ?