Jump to content

Recommended Posts

Posted (edited)
12 minutes ago, ST0RM said:

It's a flight model issue, not an obscure system that would require detailed setup. Its literally go up and fly. Can't get any easier. 

I can assure you that even the most obvious thing that the common user will try first, can remain perfectly obscure for the developer working in the "code" side, because he is working on a totaly other thing since, lets say 5 days, so doesn't even have the idea to try and check the thing that was OK and coded 6 month ago. And as gnomechild explained there is so many things that can occure and make the dev thinking all is Ok and finally no... Usualy developper work on their own "copy" of the software, the published "copy" is not the same...

Edited by sedenion
  • Like 4
Posted

I hope they can sneak a fix for the refueling glitch in with the next FM update, that glitch really ruins the F1 aswell, having to reslot after every mission because my jet now weighs 3.5 tons less and flies like an F-16A.

  • Like 1
Posted
1 hour ago, sedenion said:

I can assure you that even the most obvious thing that the common user will try first, can remain perfectly obscure for the developer working in the "code" side, because he is working on a totaly other thing since, lets say 5 days, so doesn't even have the idea to try and check the thing that was OK and coded 6 month ago. And as gnomechild explained there is so many things that can occure and make the dev thinking all is Ok and finally no... Usualy developper work on their own "copy" of the software, the published "copy" is not the same...

 

I work with coders everyday. They makes edits, then I check that those havent broken anything and approve it (or not) before it gets pushed. And yes, its on an actual flight training device. It's a simple process.

I like the dev and the F1, but giving them a pass on an easy issue isn't the solution. I hope they learn from this and tighten up their process so it's not repeated. Right now people are wanting the F1 for a free trial. I've recommended that they buy it outright as it was that impressive from the start. With this FM, it's not flyable in a controlled manner. That is game/module breaking and warrants a quick fix. 

  • Like 2
Posted
9 minutes ago, ST0RM said:

I work with coders everyday. They makes edits, then I check that those havent broken anything and approve it (or not) before it gets pushed.

You work in the big structure where one or several people are here to verify. Not everybody have such luxury.

  • Like 1
Posted (edited)

Now the Mirage F1 is better for dogfighting.

I'll let the Aerges guys do their job, is a wip, patience.

 

Edited by Tavo89
  • Like 1
Posted
22 minutes ago, Tavo89 said:

Now the Mirage F1 is better for dogfighting.

I'll let the Aerges guys do their job, is a wip, patience.

 

 

I like the new engine power and STR, feels good when isolated from the issues we are having right now

  • Like 1
Posted
2 hours ago, leonardo_c said:

I am struggling a lot to fly with a single magic, seems harder than before.

I haven't noticed that. Though I wonder about it overall when compared to other wingtip modules like the F5. 

  • Like 1

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted

This issue has happened a lot of time with all previous modules. It is an early access like many modules. Lot of times devs suffers pressure to integrate changes before one day in order to publish the OB patch. Devs work is just make the module better and more completed in successive patches.
So please. Leave devs do it their job. They already have the fix, are waiting next update to repair this.
I also work with a lot of devs in my job and Im in charge of testing all new software and hardware updates. If you know something about code programming you know this kind of things can happen from time to time.


Enviado desde mi SM-G981B mediante Tapatalk

  • Like 6
Posted
3 hours ago, chichowalker said:

This issue has happened a lot of time with all previous modules. It is an early access like many modules. Lot of times devs suffers pressure to integrate changes before one day in order to publish the OB patch. Devs work is just make the module better and more completed in successive patches.
So please. Leave devs do it their job. They already have the fix, are waiting next update to repair this.
I also work with a lot of devs in my job and Im in charge of testing all new software and hardware updates. If you know something about code programming you know this kind of things can happen from time to time.


Enviado desde mi SM-G981B mediante Tapatalk
 

Yeah I'm not worried. It's like 1 month into EA. 

  • Like 1

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
16 hours ago, chichowalker said:

This issue has happened a lot of time with all previous modules. It is an early access like many modules. Lot of times devs suffers pressure to integrate changes before one day in order to publish the OB patch. Devs work is just make the module better and more completed in successive patches.
So please. Leave devs do it their job. They already have the fix, are waiting next update to repair this.

Do you think that the current instability needs to be fixed in both pitch and yaw as well? I'm worried that the fix is limited to the yaw damping while there are issues with the behaviour in the pitch axis as well.

Posted

Chichowalker is totally right, it's internally fixed in both pitch and yaw channels and it will committed with next ED's update. Please note that the behaviour present in current Open Beta is going to change significantly in the next update.

We also have an internal fix for the bug with "extreme speed" at low altitude.

  • Like 13
  • Thanks 8

Roberto "Vibora" Seoane

Alas Rojas

 

[sIGPIC][/sIGPIC]

sigpic97175_2_small.pngAERGES-LOGO-sin_fondo_small.png

Posted
11 minutes ago, Vibora said:

Chichowalker is totally right, it's internally fixed in both pitch and yaw channels and it will committed with next ED's update. Please note that the behaviour present in current Open Beta is going to change significantly in the next update.

We also have an internal fix for the bug with "extreme speed" at low altitude.

Great, it only remain the flaps efficiency problem so 😋

  • Like 2
Posted (edited)

Has anyone tested  the STR (or ITR?) performance? According to the real manual  ''minimum turn time'' ( is that STR or ITR?) is achieved with 300kts, i=17', max AB ~ 4g's, Other parameters (altitude, ac configuration / weight etc) are not mentioned, but from my very limited STR testing at different altitudes this is not doable in dcs (where the F1 seems to turn better at speeds around 350 - 400kts). 

 

 

 

null

image.png

Edited by jaguara5
Posted (edited)
3 hours ago, jaguara5 said:

Has anyone tested  the STR (or ITR?) performance? According to the real manual  ''minimum turn time'' ( is that STR or ITR?) is achieved with 300kts, i=17', max AB ~ 4g's, Other parameters (altitude, ac configuration / weight etc) are not mentioned, but from my very limited STR testing at different altitudes this is not doable in dcs (where the F1 seems to turn better at speeds around 350 - 400kts).

image.png

Minimum time turn is apparently neither STR nor ITR, but another combined/computed turn performance evaluation.

Some data here (don't know if this is really related, but that the only thing I found):
https://arc.aiaa.org/doi/abs/10.2514/6.1985-1780

https://arc.aiaa.org/doi/abs/10.2514/8.10661?journalCode=jans

Edited by sedenion
Posted
11 hours ago, Vibora said:

Chichowalker is totally right, it's internally fixed in both pitch and yaw channels and it will committed with next ED's update. Please note that the behaviour present in current Open Beta is going to change significantly in the next update.

We also have an internal fix for the bug with "extreme speed" at low altitude.

Thank you very much for the reply Vebora, it is greatly appreciated to hear from you on the matters. please dont forget the fuel weight glitch 😉

Posted
23 hours ago, jaguara5 said:

Has anyone tested  the STR (or ITR?) performance? According to the real manual  ''minimum turn time'' ( is that STR or ITR?) is achieved with 300kts, i=17', max AB ~ 4g's, Other parameters (altitude, ac configuration / weight etc) are not mentioned, but from my very limited STR testing at different altitudes this is not doable in dcs (where the F1 seems to turn better at speeds around 350 - 400kts). 

 

 

 

null

image.png

 

Found this : 

http://www.mirage-jet.com/TURNRA_1/turnra_1.HTM

https://www.quora.com/What-is-the-instantaneous-and-sustained-turn-rate-of-fighter-planes

It can explains differences between Sustained Turn rate (STR) or instantaneous Turn rate (ITR). 

How do you estimate your turn rate ?  Tacview ? 

Riesling | FR

Specs: i7 6700K / 32 Gb RAM / SSD /  GTX 1070 + Oculus Rift S  / Saitek Rudder Pedals / Thrusmaster TWCS + T16000M

Posted
On 8/28/2022 at 8:58 PM, Vibora said:

Chichowalker is totally right, it's internally fixed in both pitch and yaw channels and it will committed with next ED's update. Please note that the behaviour present in current Open Beta is going to change significantly in the next update.

We also have an internal fix for the bug with "extreme speed" at low altitude.

Please tell me thats going to also fix the bird flying like a 20 year old shopping trolley when you have an asymmetrical loadout, ie after youve fired a missile

  • Like 2
Posted
Please tell me thats going to also fix the bird flying like a 20 year old shopping trolley when you have an asymmetrical loadout, ie after youve fired a missile
Sure!!!!

Enviado desde mi SM-G981B mediante Tapatalk

  • Like 2
Posted (edited)

@Aerges Devs

Do you have available the real aircraft's EM charts to tune kinematic aspects of the FM with, or are you forced to extrapolate/estimate here? 

Just curious 

Edited by Hummingbird
  • Like 3
Posted
On 8/28/2022 at 6:22 AM, Bremspropeller said:

And the motor quitting due to flying through the wake. 😅

 

I once heard a Kfir pilot say that you had to be careful with the wake of the missile, because the engine could shut down.

I think it happened in Vietnam to an F4 Phantom after launching an Aim-9. If I remember correctly, in the History Channel series "Dogfights", it is depicted what happened.

  • Like 1
Posted
52 minutes ago, Tavo89 said:

I once heard a Kfir pilot say that you had to be careful with the wake of the missile, because the engine could shut down.

I think it happened in Vietnam to an F4 Phantom after launching an Aim-9. If I remember correctly, in the History Channel series "Dogfights", it is depicted what happened.

In general gas ingestion issues are pretty well known and documented for different airframes, the F1 has "protection" for this modeled, or did before the last patch, it seems to be missing currently. 

  • Like 1

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
2 hours ago, Harlikwin said:

In general gas ingestion issues are pretty well known and documented for different airframes, the F1 has "protection" for this modeled, or did before the last patch, it seems to be missing currently. 

It was happening to me before the patch but not now.

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...