Jump to content

IvanK

ED Beta Testers
  • Posts

    2920
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by IvanK

  1. You can enter Western Longitudes. To do so first Select the Key next to the the Longitude entry. BEFORE typing any values press the CLR key , the Longitude identifier will change to "W", then enter the digits. Same procedure for Southerly Latitudes. If you try to do a MANUAL IP entry using this procedure for alignment you need to be quick, as the system jumps into alignment even if you have not finished entry a valid start Lat/Long. EDIT: after some more reading the jumping into alignment mode automatically is normal and occurs as soon as the system gets valid GPS data. then uses GPS position to align. .... I guess the only time you need to use Manual or last stored position is if you don't have GPS. Regardless once aligned the STEER function works as intended, Select STEER then say Airport Rng and Brg displayed are correct and work in flight. Though calling up a SB waypoint to see its Lat and Long doesn't provide any values.
  2. I can go 0.95 to M2.0 in 3:28 for 990 litres burnt Clean aeroplane Profile: 0.95/F350 Start the clock , 0.5G pushover to 10deg nose down, level at F300 accel to 650Kias , climb at constant 650Kias (Increasing Mach) till achieving M2.0. Tried the same using Mir III profile climbing at 580Kias took 10 seconds longer. Machrun.zip
  3. Another issue is filling order. In the ME the tip tanks fill firsts THEN the fuselage tanks. This is a Bug and reported in the testers area. Fus tanks should be filled first. This would then allow you to set any fuel weight in the Fus tank and therfore get any specific weight. IRL on the refuelling panel are two switches which control tip tank re fuelling you can select either No Tip tank refuel or half tip tank refuel ... not supported n the sim
  4. This nose wheel steering engaged on take off then causing the nose gear fail is a bit over done imo. The following excerpt from the MB339 Pilot training manual describes the reasoning behind having the NWS off for take off. However there is no actual prohibition in the flight manual. With that in mind I think having it on causing the failure on the subsequent landing (regularly) is bit overdone. If the take off was normal with little required NWS input then damage should not occur. Fair enough if rapid heavy use of nws at high speed was used. ... just my 2c worth. This snippet from the Flight manual is also relevant:
  5. Supersonic climb I disagree with constant Mach climbs. The so called "Rutowski" profile is the optimum way to get to any High energy state and best times to it and requires constant IAS increasing Mach climb in the supersonic schedule. The Profile in the F1 KED Pocket checklist is: Climb to 30,000' via the Sub sonic Climb schedule 500kts into 0.92M Accelerate at 30,000' to 650Kias then climb at 650Kias (Increasing Mach) to Mach 1.8 then climb at Mach 1.8 Based on a Mirage III method I think you can do better and get closer to a genuine Rutowski profile. You don't want to be going through the transonic region in level flight ! Subsonic 500/0.92M climb to 35000' Push over (0.5G) to achieve min time through the transonic region to max 10 deg nose down not below 30,000' accelerate to 650Kias At 650Kias Climb 650Kias to M1.8 At M1.8 0.5G push over to achieve M2.0/VNE If we had access to the relevant Mirage F1 Ps info this could be optimized even further.
  6. Flagged in testers area as well.
  7. Actual setting will change as a function of Slant range, Dive angle, IAS/AOA etc. But Air To Ground Guns +44mills depression is a good starting point.
  8. IvanK

    Throttle Stop

    Only way I could get this to work was to Select Slider with a curve of -35. Any setting smaller than -35 resulted in the Throttle flicking back to the idle position.
  9. How do you use the Finger lifts to get the throttle back to Stop and remain there ? Evey time I try it goes to STOP/Cut Off then bounces back to IDLE.
  10. It is grossly Wrong. Detail bug report in Closed Beta section. At present the AOA gauge is not useful. Approach speeds of a Clean MB339 with Elliptical Tip tanks versus Fuel Remaining and using the 115Kias basic Vref at 3700Kg then applying the 1.5Kts per 100Kg are below Fuel Rem Vref 500Kg 115 600Kg 116.5 700Kg 118 800Kg 119.5 900Kg 121 1000Kg 122.5 1100Kg 124 (Tips empty just full Fus fuel)
  11. So with the new datum if you needed 150mills before then adding the 44 mill that the datum has been corrected then the total depression now required is 194mills ... you have up to 218mills to play with so dont see an issue on this delivery. If you run out of Mills you can use the bottom diamond of the reticle as your Aimpoint... its 20Mills below the centre Pipper. So with 218mills set the bottom diamond is 238mills. EXAMPLE. Lets say your solution required a Mil depression of 230mills. You know you can only set 218mills so how do you get 230mill aimpoint ? Bottom diamond is 20mill below the pipper so required Mill depression using the bottom diamond as the aiming reference (230mills) is 210mills. (210+20=230) This sort of procedure to get a few more mills was done IRL in Mir III.
  12. It has the equivalent of Boresight Auto lock.... but thats it.
  13. https://www.flight-manuals-online.com/product/dassault-mirage-f1/
  14. HTFU Brem just have to fly raw data ILS for a little while.
  15. Its not an error it was previously. The zero mills datum was fixed in 2.8. Previously it was 44 mills to low. With the correction it means any previous settings should probably have 44 mills added to them. The test to see if the datum is correct is to wind on mills until the reticle is centered on the cross it should read 87mills +- 6 mills. (Source Flight Manual) It now does this. The Mean Gun Bore line is not coincident with the FRL/ZSL in the Mirage F1
  16. 0 Mill datum has been corrected in Ver 2.8... (Raised by around 44mills) so some Depression values may need to be rejigged. Also the reticle in AG modes no longer reacts as at Gyro sight. The reticle moves only up and down the vertical axis. This is now correct
  17. Whats the Key binding title/descriptor for Show or Hide the stick ? I think its gone in 2.8
  18. Have a read of this thread: https://forum.dcs.world/topic/308310-rudder-trim-runaway/#elControls_5044576_menu
  19. 930mb is a pretty normal minimum pressure setting on western Altimeters.
  20. No, nothing in the flight manuals anyway.
  21. Reported in the testers area. Suggested Work around for now. Take off and Land with ANTI SLIP/YAW switch in the middle YAW position. Once airborne select it UP to the ANTI SLIP position. Feedback in this thread would be appreciated.
  22. Done some testing. 1. You can get random Rudder trim take off input on Take Off 2. On landing you can get random rudder input on short final then after landing need rudder trim to centre the surface. 3. If you deselect ANTI SLIP by selecting the switch to the Middle YAW position ... all this goes away, things are far more comfortable on the landing rollout. Conclusion: ANTI SLIP Rudder trim input is occurring on the ground ... it shouldn't.
  23. Trolling deeper through the Flight manual found a couple of interesting things. ANTI SLIP is actually done by automatic rudder trim. The ANTI SLIP system is deactivated by any pilot rudder input. So it cant interfere with pilot commanded rudder. It is also deactivated by Oleo compression (Weight on wheels) . So on the ground the ANTI SLIP function SHOULD not work. I think this is the crux of the issue ... its still doing its thing on the ground then the nose wheel steering amplifies it. This oleo compression cut out is not in the text portion of the manual but in the Rudder system schematics. So given what we are seeing in the sim is a Rudder trim input that is causing the mayhem I am firmly of the belief that the cause is erroneous inputs from the ANTI SLIP system on the ground. Interestingly I have noticed some tendency to drift Left o Right on take off... thought it was was just me, but now think it might be a similar thing. Will investigate further and report in the appropriate Test areas.
  24. I have noticed a tendency for the aircraft to veer Left/Right after landing with my pedals central/neutral. Looking at this further, you can see the pedal actually displaced. The Flight Controls display also indicates about 1/3 rudder displacement. A quick pedal cycle does not fix it. However if you then centre it with rudder trim everything returns to normal. So there is something strange going on here. YAW/SLIP switch may be a player. in the Up position which is normal the Damper system is in the anti slip mode so it will both damp out yaw perturbations and also centre the slip ball. In this mode Rudder trim is deactivated in flight anyway (it is in the sim too which is correct).... which begs the question why can we centre the pedals with rudder trim on the ground with the Slip switch in the Slip switch position. Seems on the ground Rudder trim is always active. (The Flight manual is a little vague here.). So to me it seems there is some random rudder trim thing happening. In the YAW mode (middle) position) it simply acts as a Yaw damper. Now a bug that is present in the F1 is any Yaw damper input is being transmitted back to the pedals ... it shouldn't, damper inputs should just happen without physical feedback to the pedals. The flight manual specifically states this. Perhaps there is something odd happening here that is causing this odd behavior on the ground. That is a random rudder trim input displaces the pedals which then gets transferred through the nose wheel steering system and appears to the pilot as an uncommanded input and directional PIO's ensue. So maybe try with the Anti Slip Yaw switch in the centre or YAW mode and see what happens .... Off to test
×
×
  • Create New...