-
Posts
844 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by jaguara5
-
Wrong thread - deleted
-
I was dreaming to fly this variant and do Cold war / night / frozen winter / anti ship attacks in the Baltic sea.
-
p. 111 and 252. Should also be mentioned, that when mag slave is commanded but the ir seeker cannot lock the radar target, the circle will be blinking inside the radar square. Would be nice to provide also a picture with the circle inside the square. p. 35 (mag slave button functionality). ''AA Mode: It slaves the Magic missile seeker to the radar or viceversa. Only works when there is a locked radar target or a magic locked target [since the button commands also radar to seeker slave] and Magic missiles have been selected ... ΄΄. Also i'm not sure the last sentence (and Magic missiles have been selected) is correct, because i think the slave function is working in CAN mode also.
-
Yes, the bug is [REPORTED] not yet [SOLVED] and judging from razbam's latest changelog for the upcoming update it seems that the bug will still be there. Ignore the link above, initially there were 2 different threads (one in september and one in october) for the same bug, with that link i was reffering to the first one. Both threads got then merged to the current one.
-
Day 1 buy .
-
If anyone is interested to see in deetail the various cockpit variations and differences between the F1 versions here is a good book http://www.aerostories.org/~aerobiblio/article5993.html https://dogfight-editions.com/fr/hor...serie-n01.html The CE seems to be very close to the French F1C-200.
-
Fantastic news! Will an english labbeled cockpit be available?
-
Nice interview! Regarding the eurofighter hotas. I have asked winwing 2 weeks ago on their discord channel if there is a chance to build one. Tonylin409, who is working with them, said that he will move heaven and earth try to convince the team to do something of it. Perhaps you could get in contact with them also.
-
Is there a chance to see an F-14 throttle?
-
Sure. I disabled real time protection in Malwarebytes (all 4 tabs). Did a dcs repair. And launched the game. After i exited the game enabled again Real time protection which i have to disable every time before i start the game.
-
Thx! I have already sent you a PM. For the time being ignore it please. Malwarebytes seems to be the problem.
-
Is there a support contact where i can request help from heatblur? I have a ''dlc f-14 is not authorized' message that prevents me using the module. Thank you
-
Given the fact that he didn't blacked out and that the plane was still in one piece and able to flying (actually able to fighting) it's fair to assume that he didn't exceeded the (above mentioned) 13g limit. But we went OT. Fact is about the turn rate, that according to HB the problem is already fixed interanlly (if i remember correctly).
-
They must ask also Fereydoon ''Ferry Ali'' -Mazandarani, who flew real war dogfights with the F-14. https://www.reddit.com/r/hoggit/comm...re_a_story_by/ According to him, the airframe became bent by 11 degrees due to over g, which damaged the electrical wiring within the plane. As a consequence he was unable to fire his weapons (in combat not in training).
-
Is the VF-84 ''Final countdown'' livery that was posted in HB facebook video about the yaw string available ? Can't find it in the mission editor
-
[PENDING FUTURE UPDATE] HUD bugs / inaccuracies
jaguara5 replied to jaguara5's topic in Resolved Bugs
Updated track showing 1. wrong speed / altitude indication in CAN mode, should be like in MAG mode in the depressed position. 2. wrong MAG (and CAN) scale / indication as stated above (at 1.9 nm range the numeric indication should change to 35(00m) and the DLZ scale changes also (35 is the top part of the DLZ). This is valid for MAG and CAN, in 530D (not showed in the attached track file) the indication should remain always in nm. 3. wrong DLZ / indications while in CAN mode as stated above (at about 1000m the DLZ is removed and range is indicated only with the counter clockwise moving piper) 4. wrong indication after last missile is fired as stated above (the outer circle , the TIR indication and the range markers on the DLZ should be removed) 5. instantaneous symbology change (as stated above, with MAG lock the inner circle appears first with the small intercept square in the middle, after ~ 0.5 second the second TIR outer circle comes in and onle after that the square starts moving), must be confirmed with SME. 6. dashed part of the snake line is missing as stated above. 7. (new observation) the altitude alert arrow on all videos that are in the net is blinking, in DCS it is steady. Not showed in the attached track file, can be confirmed with SME Resolved. (Edited) hud track ..trk -
https://forums.eagle.ru/forum/englis...05#post6470105 According to this post there are '' ... alot of big changes coming .... '' for the Mirage. Can we have an idea what systems will be improved / debugged? Are the upcoming changes limited to above mentioned 4 only or should we expect more of them?
-
I'm ashamed to ask, but where exactly should i place the downloaded folder?
-
[PENDING FUTURE UPDATE] HUD bugs / inaccuracies
jaguara5 replied to jaguara5's topic in Resolved Bugs
The closure speed is different between PIC and PID (intented?). Also the range indication for the 530D changes below 0.6 nm to m as it shouldn't, according to the video reffered in the previous post closure speed bug 630 range 3..trk -
I would pay for an F-16 Block 30 / F-16N (ok it has APG 66 but , anyway ...).
-
[PENDING FUTURE UPDATE] HUD bugs / inaccuracies
jaguara5 replied to jaguara5's topic in Resolved Bugs
Another video (from AdA - ec 2/5) posted in discord that supports some of the above reported bugs (like that the speed and altitude indication in CAN mode should be in the depressed position, also watch 2: 24 - 2:29 the exact distance point at which the DLZ is removed in CAN mode (around 1000m). It seems also that the range indication on the dlz in CAN mode (before it is removed) is identical with that of the MAG mentioned in the first post, we can see the indication 17 = 1700m, going down to 10 = 1000m, in game the indication remains in nm). Edit - the only mode at which the indication remains in nm, and doesn't convert at all to m, seems to be the 530, watch this video at the very beginning Finally, there is the dashed part of the snake line visible. According to real pilot, the dashed part starts 50 or 100 m before the 300m mark, depending on speed (or AoA can't remember as i can't remember the exact speed / aoa value at which the dashed part extends or gathers respectively to 50/100m before 300, input from AdA is needed). The dashed part shouldn't be used for aiming due to the close distance. -
Already reported. https://forums.eagle.ru/showthread.php?t=286920 The position of the cone is wrong if you select boresight after vertical scan (you can see the wrong position with the bar on the left side of the VTB). Boresight is working if selected after horizontal scen.