MYSE1234

If you got TerNav working and sending fixes to the nav system, doing a radar fix is just going to make it less accurate. If you get a 5 from the system, there's no need to make a fix as the fixes from TerNav are dead accurate.

Yeah, that's fair. BX are more suited for pre-planned mission targets. Where you can share a singe flight plan for a strike package, but you each have a separate BX waypoint for the targets. That's what I/ we have been using them for at least, other than for the RB15s, works great. For TOO a fix in SPA is probably better tbh, it not being connected to the route...

BX 6-9 are only used for RB15 if they are loaded, otherwise they are just "waypoints" outside the nav polygon, together with BX1-5. BK90s work with BX points, I used it yesterday. If you have no BX waypoints already and find a target, you just have to select BX1 for example, hold T1, that will make a waypoint being created 10 or so km in front of the aircraft. Then you just move it to the target and press TV to make a fix. And you have a BX waypoint at your target, that you can use for pretty much any weapon.

They will fly to the selected waypoint. I think of BX waypoints as M waypoint that are out side of the nav polygon.

Adding/ using an unused "BX" waypoint sound like what you want to be using. You can do that by either selecting the "BX" WP of choice, and doing a fix. Be it radar or visual. Or you can also add them using coords like any other waypoint.

It's obviously not super accurate, but probably in the ballpark. The two rightmost lines are based on the ISA+10 line and offset from that.

I believe mine cost about €40-50 or so. I guess it depends on how much you know previously, learning everything from the start will obviously take some time, but very possible. I believe I've spent about 300-600h designing this stick. :D yeah, I know...

Thanks. Mine is indeed 99% 3d-printed, all but the ball bearings and the electronics (obviously). It's a gimbal. It's not the best one there is, but it's small enough to fit the quite small body it. The outside wall is 55mm wide both sides iirc, with a wall thickness of 5mm.

I concur.. :pilotfly:

I wouldn't say it's random, as it only shows the HUD between around -10 and +10 degrees with the trigger in the safe position. Anything outside that range it's going to hide it, unless the trigger is unsafe.. I'm guessing you're flying with RB24s loaded, they have a G-limit of 2G, in-game it's closer to 2,8G or so. The 24J and the 74 have a limit at 6G, in-game 6,5G.

I hope this image gets the point across, but this is what I think is happening. The ships are as you said moving. From the time you made the fix to when the missiles reaches the supposed target, the ships might have moved outside the missiles search area, and therefor miss. If you launch the missiles at their max range 74km, it will take them 4 minutes to travel that distance. In that time the ships have moved quite a bit. In the image, 1,9km, and that is if you make the fix directly before launching them. I'm also not 100% sure about the RB15 search parameters (I only really use two of the presets), but I'm pretty sure this problem can be omitted if you use the correct settings on the missiles. At least partly. Feel free to correct if I calculated it incorrectly.. 5kts - 600m 10kts - 1,2km 15kts - 1,9km 20kts - 2,5km IMAGE NOT TO SCALE

https://forums.eagle.ru/showpost.php?p=4483353&postcount=72

If I'm reading the charts correctly, MTOW without AB should be around 15500kg at ISA and ISA+10. At ISA -15 and ISA-30 it's around 16000kg. A fully fueled jet weighs about 15235kg, a fully fueled one with a tank is 16430kg. Either that's the MTOW, or they just didn't bother calculating higher weights. Source: AJ37 SFI Del3

A blinking "-" would mean that the selected weapon has some sort of fault to it, or is used in a uncombinable weapon loadout. Like mixing RB15 and BK90s. A blinking "1" is correct as that shows that the selected weapon is working correctly, and can be used. A "0" shows that the station is empty or that the weapon has been dropped/used.

1. I wouldn't say that that area was well known, as that mission was pretty much the first time at that airfield. Especially at night. 2. It is indeed not that easy to use currently. 3. The target was clearly visable to me. It definetly disappeared thanks to the low res on the video. The video seems to be playing a bit too fast too. The audio is also not synced, it get's worse the further in the video you are. If he wants more videos I'll make sure to fix all that. :thumbup: 4.There was indeed some cross wind. Regarding the TILS, I never follow the side (left/ right) commands as they will just guide you into nowhere. I do try to follow the glide slope as best as possible though. As far as I'm concerned visualy lining up visualy is safer and quicker when landing. 5. Landing lights are not a thing as far as I know, we only have taxi lights. The fin was bugged as I was using ToT with the Rb15 (they hit 2s early btw). Might want to have a look at that AoA indicator. You as a pilot should probably know that exists. Also if I was at the alpha that the fin indicated it should be blinking and there should be an audible tone. I switched to "LAND NAV", 40-something km away from L1. The sound you heard was me setting it to BER after landing. It's related to "3." above. Thanks for your review on my flying. It's possible to do night flying as you've now seen. It might not be very safe, but then again is any night flying compared to daytime? I think I'll be quite alright not joining that squadron of yours, thanks very much. *cough*Rule 1.2*cough* :pilotfly: Yes, lets go back to change log talk.

I am indeed currently part of one yes. I'm currently the squad(ron) lead for AJS37 in TAW EU. Thanks for the offer though. Said video:

I think that 1.2 rule also applies to you too as far as I know. Is that why you don't have your location added? But yes, let's keep this civil. I'll quite happily post a video of me flying that mission, if that makes you belive that I can fly at night. Just have to figure out how to record the VR view first. :) I'll post it here, not going close to Facebook.

Are you mad or something?! I quite simply corrected you in that there is/was a night filter in the real jet in that other thread. I also acknowledged that there is a problem with the taxi light, but that I/we were able to taxi and succeed with our mission anyway.

Yes, it's currently broken. The light from it is very very dim. There was a DCS update that changed all the lights some time ago, and the taxi light has not yet been updated to the new lighting.

As the real thing is a wheel that you turn, you have to click/ hold that "RAlt+RCtrl+F" a few times for it to fully make it go into "night mode". When it's at its lowest setting it is very red. You can then tune the brightness with the "radar brightness", or a mix of the two. It works very well, and makes the radar fully usable at night.

I have actually, me and 4 others. It's not easy to taxi by any means, but it's very possible. I did an attack with RB15s, ingress 10m altitude. Radar fix and fire, then back to base and land. And you quite clearly said there wasn't a filter for the radar, which was what I was answering to, but I digress. Use of NVGs is blasphemy, and should not be used in a Viggen. :smilewink:

...

Looks quite good to me. Much much better than before. Now all that's left is the A/B of your own A/C. Which TBF you don't really see anyway.

The spreadsheet is updated. And the answer to what has changed is, not much. The only notable change is that you don't need afterburner to keep 92% at 4000m. The fuelflow at 92% does seem to keep to the correct "curve" (albeit a bit too high, 0,14%/min), but that goes wrong at 5000m, as with the other things.

Updated AI afterburner. Might want to have a look at an AI Viggen at night. :smilewink: But yes, the AB on your own aircraft is still barely visable.