3000 Black Jets of Allah

Regular updates are normally on the last Wednesday of the month.

RAZBAM and the M2000 don't use the Super 530F, they use the D. So the 530F for the F1 doesn't have to have the same firing and flight envelope as it is a completely different missile.

If you are clicking out of the map marker box with the X then you are deleting that map marker. To close them you need to press the - instead. I hazard a guess that they're not importing because you're deleting them straight after you create them.

The RB05 | BOMB position of the rotary isn't a selectable one, it's merely the identifier for the inner (BOMB) and outer (RB05) rings of the weapon selector. It also don't start in RB05 | BOMB, it starts in SJO | PLAN.

Now that the Mavericks on the Viggen are using the ED API they need 3 minutes to align after weight off wheels, unfortunately this means no more Maverick sight on the ground anymore.

Ohhh my bad, I was thinking you were referring to a new livery. Sorry about that!

What new paintkit? There wasn't one added in the update.

Blanking the number just shows a dynamic tail number of 00 on the aircraft unfortunately.

Can confirm that unlimited ammo breaks the mavericks after the first one is fired.

Bit sad that it looks like the MYSE mod stuff didn't get added according to the patch notes

How do you get your HSD to look like that with the compass lines coming out from the center? I think I've seen it like that in 1 or 2 videos but never found a way to show anything like that on it.

It's all working fine again, I decided to test after the update and there's no lag. I'll keep that in mind if it happens again so thanks Also just wanted to say that I love your work, really appreciate the things you've created for the community!

EDIT: 18/11/2022 - Decided to test after the latest patch and everything is working fine again with no changes on my end as far as I can tell. Just started getting massive lag when the exportscript line is enabled in my Export.lua file. Was working fine last night and loaded the game today with zero changes and I get around 2-3fps instead of 100. Can fix it by commenting out the export script line but that obviously disables the whole thing. Had a look at my DCS log and there is nothing in there that seems to be an error relating to the export or slowdown. I thought maybe it was a GPU issue because when the game is running my actual GPU core load is around 2-3% and then if I press escape to pause the single player mission it goes back up to 99% and it stops lagging which is due to the fact that the exportscript isn't polling data when paused (I think). Even though the GPU usage is low the memory is completely full like it usually would be. Tried GPU driver uninstall with DDU and then a reinstall of the latest one which is the same as the one I uninstalled but no dice.

I honestly think it might be, I can't remember exactly but the times it's happened I think I've jettisoned the empty maverick pylons to go faster so that could be it.

Yep this also happens to me, kind of looks like the scope is looking at part of a pylon but it won't let you move it. No amount of uncaging or slewing works and restarting the jet doesn't work either. After rearming with mavs it happens and then if you rearm with something else like bombs whenever you unsafe the trigger the mav scope lights up and shows the bug, despite there not being mavs on the jet.

The crashes have nothing to do with mods, I've done a full game repair and extra file removal and renamed my saved games folder to create a full new one and I crash when trying to join aircraft on a completely vanilla game with zero mods.

Really strange, tried another mission and everything was working, got range data for the 530 and had a box around the locked aircraft again. Maybe 10th time was the charm lol

Yeah I've tried single player missions and multiplayer both cold start and start in air and no dice unfortunately. In all honesty I don't mind not having the range stuff but the lack of a HUD symbol for what you have locked is really bad.

With the introduction of the new 2.8 patch the Mirage F1 received proper ranging information on the HUD. My question is whether this actually works for anyone else? The only time the ranging is displayed is if I'm in 300m or 600m gun mode and that's it, the tape always displays 0. I've tried with 530s, sidewinders, and 550s and nothing. They also seem to have removed the orange box that appears around the target you have locked on your HUD, is that the case for anyone else?

Just tested with the new 2.8 patch in case they had silently fixed it but it's still bugged. Targets that were 20k feet above me could be seen with +2 instead of +20 on the radar.

I've been giving that a go and it's kinda hit or miss, depending on the range to target and the distance you move the BX7 point the missiles can end up reaching the target too far apart so the enemy gunners just shoot them down one by one. I might have to keep messing around with it to find the exact amount of BX7 movement that results in them both reaching the target at the same time. I figured it must be because I'd tried everything I could to make it consistent lol.

Yeah I figured it was a dodging technique, I was more curious about controlling it. I can't seem to reliably make them both go opposite ways which would increase the chance of a hit instead of them both going the same way.

I was wondering if anyone had some more info on how the RB-15F swerves to the side before it impacts a target. No matter what I do I cannot seem to reliably get one to left and one to go right. Sometimes they do go separate ways and come onto target from different sides, making the enemy defenses focus one so the other hits. But other times they both swerve left or both swerve right and the line themselves up nicely for the enemy guns to shoot them both down. I have tried in pre-planned via F10 marks, pre-planned via the radar with manual fixes, and also just the NAV mode straight shot to no avail.