Jump to content

Rlaxoxo

Members
  • Posts

    1733
  • Joined

  • Last visited

Posts posted by Rlaxoxo

  1. well, still the throttles issue here...

     

    perhaps its just my module ?

     

    Everything works fine on my end try reinstaling the module

     

    Someone had similar problems and got it working again

     

    Anyone having issues keeping straight down runway? Trying to balance rudder is a chore

     

    Takeoff on NTTR is a pain aircraft go left and rudder is useless.

    TDC still bad for me too.

     

    You guys, no offense... but I assume I am not the only one who starts to get a little bit annoyed about the fact that some of us still can not even fly this thing because of the Keyboard issue... particularly because someone mentioned on the 25th/26th its an "obvious error" and it should be fixed soon...

     

    so any update here is very welcome...

     

    thanks..

     

    any idea when they plan on fixing Keyboard flight for this thing? rudder, throttle, aircraft movement?

     

    well, still the throttles issue here...

     

    perhaps its just my module ?

     

    Reinstall your Mirage module all of the issues above are fixed and work just fine

     

    I have no problems taking off and going straight

     

    You're ether flying in 1.5 where patch isn't out yet or your installation for 2.0 got borked try to reinstall it

  2. Since we got no love from RAZBAM or ED on the key bind front, I'm trying to edit some of your code. I use a pulsed input toggle switch to operate some switches in my pit. The switch i use in my pit for every aircraft master battery is connected to a desktop aviator 2235 board which sends a pulse when you flip the switch which allows me a toggle feature, which comes in handy. For example your coding for the master battery requires you to have two buttons programmed to turn it on and off. i've tried editing your lua but when i flip the switch in my pit it turns the switch on then off in the sim.....i know that sounds confusing but its avoiding me how to get this thing to work right. i have been editing luas for a while now for key bind issues but this one is stumping me. here is my code i'm using....i changed it to have value=up 1 after the cockpit device id:

     

    {down = 3520, up = 3520, cockpit_device_id = 8, value_up= 1, value_down= 0, name = "Custom - Engine - Main Battery Switch Toggle", category = "Engine"},

     

    taken from your code:

     

    {down = 3520, up = 3520, cockpit_device_id = 8, value_down= 0, name = "Custom - Engine - Main Battery Switch Off", category = "Engine"},
    {down = 3520, up = 3520, cockpit_device_id = 8, value_down= 1, name = "Custom - Engine - Main Battery Switch On", category = "Engine"},

     

    any insight would be greatful

     

    Well basically if you want to make a toggle bind you would need a name of the bind function of that would always change the value by 1 step.

     

    I haven't really bothered to look deeper into this since I usually use On/Off switches so I just manually change the value instead of calling the function

     

    But basically it would look like this

     

    {down = iCommandplaneBattery, name = "Custom - Engine - Main Battery Switch Off", category = "Engine"},

     

    Now I don't know the function to this so it won't work unless you get the right function name but ya

     

    Every time you press the button it would make it go up and down with the same press

  3. Folks, the team is scattered right now due to commitments that could not be dismissed. CptSmiley still has a week before his return. He is aware of your comments but cannot do anything until his return :'(

     

    We will keep fixing the aircraft until it is good (not perfect, perfection is unattainable and it is the enemy of the good).

     

    Some stuff, like axis movements or ffb are scheduled to be included later, when their main systems are upgraded (e.g: The TDC movement will be overhauled when the radar gets upgraded).

     

    We got this "critical fix" out before we enter into our upgrade schedule, where all the bugs will be dealt with.

     

    Well this new patch certainly fixed alot of core plane issues and I'm grateful cus it made the plane even better hehe : )

     

    FBW Gain is really useful switch now and I really like it, much better then flipping around and killing your self switch

     

    lots of great stuff came with it but people like to overshadow it by some other tiny stuff

     

    Not that I'm complaining you guys are probably swamped with work and it I think you guys will make good on future fixed however

     

    Here are my 2 most noticeable bugs that came with this patch

     

    1 - Mirage has a weird rudder jiggle effect after rolling with a FBW Spin switch ON

    [ame]https://www.youtube.com/watch?v=Nhj5VPVPpeM[/ame]

     

    2 - The max speed isn't reflecting the Flight Envelope graph, Feels like the Transonic/Supersonic Drag got over tuned as seen in the following image

     

    attachment.php?attachmentid=132920&d=1452912739

  4. Yes, but only in between 31k feet and 54k feet or so, approx. higher or lower its slower. :smilewink:

     

    Currently around 35k - 50k feet I can only manage to barely reach the speed of mach 2.01 and at low altitude around 3,000 feet I can reach the speeds of mach 1.08

  5. wiki is not a great resource, its a start, but a good resting place to get information:

     

    Topolos work is some of the better works i've seen to date, and since its referenced as a viable reference from the devs, i'll post the relevant chart for this thread i belive:

     

    Awesome stuff thanks for that

     

    So If I'm reading this correctly it's saying that with clean config the max speed is around 2.2 Mach?

  6. Ok, according to the Level flight max AB the fastest speed would be the lowest altitude of the structural limit, as in clean config between 30k and 55k feet is the structural limit. thus the max speed should be attained just above 30k feet which is M2.2.

     

    M2.2 at 30k feet is about 1296 Knots TAS or 2400Kph TAS as M1.0 at 30k ft 589kts/1091kphTAS

     

    Clearly something has gone wrong. i suspect a typo in the math. its just to gross an error.

     

    With the mirage in this patch there is no possible way to go pass the Mach 2.07

     

    No matter how hard I try

     

    I know it won't mean much but just gonna post what's stated on wiki

     

    General characteristics

     

    Crew: 1

    Length: 14.36 m (47 ft 1 in)

    Wingspan: 9.13 m (29 ft)

    Height: 5.20 m (17 ft)

    Wing area: 41 m² (441.3 ft²)

    Empty weight: 7,500 kg (16,350 lb)

    Loaded weight: 13,800 kg (30,420 lb)

    Max. takeoff weight: 17,000 kg (37,500 lb)

    Powerplant: 1 × SNECMA M53-P2 afterburning turbofan

    Dry thrust: 64.3 kN (14,500 lbf)

    Thrust with afterburner: 95.1 kN (21,400 lbf)

    Performance

     

    Maximum speed: Mach 2.2 (2,530+ km/h, 1,500+ mph) at high altitude

    Range: 1,550 km (837 nmi, 963 mi) with drop tanks

    Ferry range: 3,335 km (1,800 nmi, 2,073 mi) with auxiliary fuel

    Service ceiling: 17,060 m (59,000 ft)

    Rate of climb: 285 m/s (56,000 ft/min)

    Wing loading: 337 kg/m² (69 lb/ft²)

    Thrust/weight: 0.7 at loaded weight

     

    But overall Raznam really did a great job this patch

     

    GJ Razbam team!!!

     

    Just look over the drag again if you're reading this

  7. its a animated switch sound thats bugged i think in mirage click click click sound looped.

     

    already been noted i think.

     

    We're not talking about that issue here ... this is another issue with the Engine afterburner going on/off when your engine is idling

  8. I did some dogfights with the new update. The Mirage is much slower and handles less well. It seems like we were cheating with the first on steroid version against those migs.

     

    she is much less powerful but more realistic I would say. Before, in the middle of a dogfight, you could skyrocket and they would never catch you.

     

    That's not the issue we were talking about that issue has been fixed and we don't have problems with that

  9. Thanks!!

     

    Was just flying the Mirage and had like 6 or 8 red lines again.. radar range, etc... losing bindings etc...

     

    /edit..

     

    Had to rework a few key assignments and change m Hotas setup, but wow!!!.. finally I can make this jet work for me!

     

    I must say that as far as these key assignments go I was pretty disappointed with this patch. Thank You!

     

    Glad it worked, hf man

  10. There is to much drag In mirage atm I can feel it

     

    When you ran out of gas and you try to glide you super slow down to 300 kph

     

    In an F-15 you can glide pretty efficiently around 600 kph or lower but with the mirage now I fly like a brick

     

    Here's the pictures

     

    #1 - Low altitude max speed - Mig2-1bis

    5jNKSjy.jpg

    I could go 30 kph faster but my engine died

     

    #2 - High altitude max speed - Mig-21bis(IAS)

    5csc3b1.jpg

     

    #3 - High altitude max speed - Mig-21bis(TAS)

    mUiNq4e.jpg

    It was a bit higher The engine turned off while i was taking the screenshot

     

    ________

    #1 Mirage - Low altitude max speed (IAS)

    I7ryQK4.jpg

     

    #2 Mirage - High altitude max speed (IAS)

    BrTXCAM.jpg

     

    #3 Mirage - High altitude max speed (TAS)

    lVSpQRY.jpg

  11. Rlaxoxo's results may very well be realistic.

     

    I calculated the thrust to weight ratios of both aircraft at gross weight.

     

    MiG-21bis

    8 725 kg

    71 kN static thrust with afterburner

    T/W = 71000/(8725*9.81)= 0.83

     

    M2000-C

    13 800 kg

    95.1 kN static thrust with afterburner

    T/W = 95100/(13800*9.81)= 0.70

     

    So you're saying Mig should be faster then Mirage acceleration wise?

     

    Doesn't make sense

  12. I just did a side by side comparison with a friend Mig-21 vs Mirage

     

    We were both around 700 Kph going straight at 3,000 meters

     

    On 3 we punched in full AFB and Mig-21 went off like a rocket and out-accelerated Mirage like it was nothing

     

    And to top that off I had higher top speed then

     

    Mig-21bis - 1270 Kph - Top speed IAS

    Mirage - 1145 Kph - Top speed

     

    I'll upload a video shortly

  13. I think Razbam overdid the engine performance and drag fixes a bit

     

    Up high 9,000 - 11,500 I could barely hit Mach 2.05 (1040 Kph IAS)

     

    In Mig-21 If I don't slow down I hit the wall of Mach 2.3 (1290 Kph IAS) and flame out my engine

     

    At low altitude basically what's happening is the following ...

     

    Mirage is accelerating quite nicely and then after you reach the 1140 Km/h IAS you hit a brick invisible wall and instantly slow down to 1160 - 1170 Km/h IAS and that's your top speed

    ___

    Clean config 100% fuel

     

    Here's the pictures

     

    #1 - Low altitude max speed - Mig2-1bis

    5jNKSjy.jpg

    I could go 30 kph faster but my engine died

     

    #2 - High altitude max speed - Mig-21bis(IAS)

    5csc3b1.jpg

     

    #3 - High altitude max speed - Mig-21bis(TAS)

    mUiNq4e.jpg

    It was a bit higher The engine turned off while i was taking the screenshot

     

    ________

    #1 Mirage - Low altitude max speed (IAS)

    I7ryQK4.jpg

     

    #2 Mirage - High altitude max speed (IAS)

    BrTXCAM.jpg

     

    #3 Mirage - High altitude max speed (TAS)

    lVSpQRY.jpg

×
×
  • Create New...