Izgud Posted June 8, 2016 Posted June 8, 2016 Great job on the Mirage so far! It's coming along quite nicely, and I'm happy to see such a level of participation in discussions from RAZBAM during the beta process. Since you guys have been so receptive, I figured putting effort into a few minor suggestions would be worth my time. These little things have been bugging me for a while now: 1. Altitude readouts on the HUD should be reporting in tens (980, 990, 1000, 1010, etc). 2. HUD refresh rate, especially for speed and altitude readouts After further research, it appears as if this may be accurate for the variant modeled in DCS. I've seen some Mirage HUDs with speed/altitude refresh rates of about 6.3Hz, which makes for a very obvious slideshow effect typical of many HUDs, but others that are more instantaneous like the one in our DCS model. Input from other forum users still welcome! Instead, my #2 will be this: VSI and altitude seem to respond instantly to changes in actual altitude/vertical speed. Shouldn't there be a slight delay? 3. KCAS is incorrect - the calculation does not take temperature into account. This is something to look at in the FM as well if incorrect cockpit readouts were used for performance tuning. The altimeter correctly reacts to temperature. Attached is a mission with an A-10C and M-2000C side-by-side at 300 KTAS and 20,000 feet true altitude. Weather conditions are default aside from a temperature 50°C. Indicated altitude is lowered by a similar amount on both aircraft when compared to true altitude reported by the Ctrl+Y info bar. However, only the A-10C correctly shows a reduced airspeed readout of about 213 KCAS while the M-2000C seems to be using the simplified info bar "IAS" calculation of about 219 KCAS. The aircraft's systems and the Ctrl+Y info bar should only match when atmospheric conditions are standard (15°C).KCAS_vs_temp.miz 1
Frederf Posted June 8, 2016 Posted June 8, 2016 I would like to add that the mechanical counters, e.g. altimeter digits, could use a look at. Most modules fail to do this correctly and the Mirage is one of them. The progression 19,900...19,950...20,000 shouldn't look like 19,900...10,050...20,000 like it does now.
Gliptal Posted June 9, 2016 Posted June 9, 2016 Nice finds! Since we're at it with the mechanical counter, the engine RPM tenths digit also changes suddenly rather than being animated like the unit digit.
Murdock01 Posted June 9, 2016 Posted June 9, 2016 little bugs On multiplayer radar won't lock property, vertical scan won't show up and few other things, altimeter not displaying correctly, Manual fail to correctly introduce IFF.
PiedDroit Posted June 9, 2016 Posted June 9, 2016 On multiplayer radar won't lock property, vertical scan won't show up and few other things, altimeter not displaying correctly, Manual fail to correctly introduce IFF.Wrong thread.
Gliptal Posted June 9, 2016 Posted June 9, 2016 On multiplayer radar won't lock property, vertical scan won't show up and few other things, altimeter not displaying correctly, Manual fail to correctly introduce IFF.Manual is still WIP.
Davee Posted June 10, 2016 Posted June 10, 2016 On multiplayer radar won't lock property, vertical scan won't show up and few other things, altimeter not displaying correctly, Manual fail to correctly introduce IFF. This is known Chris, Please check the other threads for this information. Cheers,
Recommended Posts