WildBillKelsoe Posted January 14, 2016 Posted January 14, 2016 (edited) 1.5.2 1) the fuel bingo drums, are they bugged? they don't seem to be clickable 2) the select altitude drums (hey its drum day!!!), autopilot 3rd from the bottom button doesn't follow it. 3) Mk-82's behind centerline don't seem to appear on the PCM window 4) any update on LGB-12 external model? it looks nefarious 5) no information on how to use the navigation modes/selector or to input the coords, the INU alignment, or the lat/long 6) laser code for LGB setting, how, no.. where?? 7) hud appears enlarged... also, the cut through with forward head movement like no borders (NO HAND HOLD P-51 doesn't cut through) 8- trim and FBW appears like BMS/F4.0.. are we flying a camouflaged F-16?? thank god it is not reversed pitch trim wise!!! 9) no information on approach speed schedules... minimum and controllable with 50% fuel and 2 hung 82's (above) is 160 KIAS, wobbly below 150 KIAS. 10) gun snake starts letter Z and folds into it.... 11) no TDC axis for radar slew in axis settings (I-251???) EDIT: [ame]http://metal2mesh.com/public/Manuals/Mirage2000Cv1FR.pdf[/ame] I found this, on chapter 7 page 37/51 starts to explain INU alignment procedure. In French. I know some French so I'll give it a shot (unless it is not implemented) Edited January 15, 2016 by WildBillKelsoe AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.
bzhnono Posted January 14, 2016 Posted January 14, 2016 Have you read the first thread in this forum ? and the buglist ? [sIGPIC][/sIGPIC]
Azrayen Posted January 14, 2016 Posted January 14, 2016 1 to be implemented later 2 bug reported 3 PCM ? 4 no comment 5 to be implemented later ; announced since beginning 6 to be implemented later ; other topic has information 7 uh ? 8 no. But it's beta EFM. 9 manage approach with AoA not speed. 14° AoA as published. 10 uh ? 11 bug reported. Agree with previous poster, BTW.
PiedDroit Posted January 14, 2016 Posted January 14, 2016 10 already reported (uninitialized data in snake first segments)
gospadin Posted January 14, 2016 Posted January 14, 2016 For #3 are you mixing A2G weapon types? That's not supported by the M-2000C's computer. My liveries, mods, and missions for DCS:World M-2000C English Cockpit | Extra Beacons Mod | Nav Kneeboard | Community A-4E
WildBillKelsoe Posted January 15, 2016 Author Posted January 15, 2016 (edited) Yes I am. I know its not supported by the PCA but it doesn't say which mixes should not be together. Also, if that is the case, then one type of a/g weapon should be used, and I had 3 types (clusters, gibby-you 12, and mack 82) loaded. PCA only sensed the first two. Edited January 15, 2016 by WildBillKelsoe AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.
Azrayen Posted January 15, 2016 Posted January 15, 2016 Well, I'm not sure about DCS, but IRL it's one type at a time only, due to avionics limitation (balistic calculator IIRC). This is mentionned in Razbam's manual. Now, you're free to experiment with pushing the limits... but be aware you're "out of bounds" so problem may arise (and in fact perhaps DCS is more lenient than reality, here) ;)
nomdeplume Posted January 15, 2016 Posted January 15, 2016 No mixes should be used together, that's why it doesn't say. The actual behaviour of the PCA with mixed loads is likely 'unknown' or even 'undefined'. The current DCS implementation seems to treat all Mk-82 type weapons as if they're the same (i.e. GBU-12, Mk-82, Mk-82SE), so it's completely impossible to release more than one variant of this bomb.
WildBillKelsoe Posted January 15, 2016 Author Posted January 15, 2016 could the 30 mm be used as antitank? ala A-10C? Err... like load combat mix, hei, tp? AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.
statrekmike Posted January 15, 2016 Posted January 15, 2016 could the 30 mm be used as antitank? ala A-10C? Err... like load combat mix, hei, tp? Not really, the gun is entirely different and while it can take out the usual soft targets, lightly armored vehicles, and (obviously) aircraft, it is not a anti-tank weapon like the A-10's gun. Think of it this way, the M-2000C is pretty much a anti-air platform, it can do some light bombing but it was never really built to do that role as well as it does intercepts and general fighter work.
gospadin Posted January 15, 2016 Posted January 15, 2016 No mixes should be used together, that's why it doesn't say. The actual behaviour of the PCA with mixed loads is likely 'unknown' or even 'undefined'. The current DCS implementation seems to treat all Mk-82 type weapons as if they're the same (i.e. GBU-12, Mk-82, Mk-82SE), so it's completely impossible to release more than one variant of this bomb. It treats them all as the first type loaded, however it doesn't treat them the same. high drag uses CCIP, low drag uses CCRP, and they'll have corresponding different symbols on the weapons panel My liveries, mods, and missions for DCS:World M-2000C English Cockpit | Extra Beacons Mod | Nav Kneeboard | Community A-4E
Recommended Posts