Fulgrim

Hi @Sneep, I'm trying to use this with Open Mod Manager but every time I double click on it it closes directly. I have placed the .exe on my /OMM/Saved Games/Library folder. Thanks.

Question, is it the same for enemy AI if the plane's lights are on or off at night in terms of getting tally over us? Thanks.

Tolerances have been changed, the FPM needs to be exactly over the ASL if you want to release.

Hi, I week ago I opened this ticket because my Paveway III's weren't tracking sometimes. After some testing, I can confirm that the issue is not with the bomb but with the Tpod. When lasing, if for some reason the laser trigger is released and then immediately pressed, the Tpod won't re-lase. There needs to be a second between trigger presses for the Tpod to function properly. I believe this is negative because some joysticks with little travel can be unadvertedly released and pressed in the same 10 milliseconds, which stops lasing. Since it's easy to test, no track needed? Thanks.

After some testing I can confirm that, in the case of the GBU24, this is not a bomb problem but a laser problem. When releasing the laser trigger and immediately pressing it again, the TGP won't lase, thus the bomb can't track. I will be opening a corresponding ticket in the Viper section. Thanks.

After some testing I can confirm that, in the case of the GBU10 and GBU12, the FPM has to be exactly over the steering line if these are to be released. Can we please get the manual updated and the tolerances for the FPM deviation published? Thanks.

Hi, did any mod had the chance to review this? I tried setting different release angles on the CTRL page, since a squad mate suggested it could be related, but I encountered the same behavior with 45º and 0º. I'm always launching on level flight below M1. Thanks.

Hello, with the Viper and a mixed payload of GBU12/GBU24 the 24's didn't track the laser although I was on a level flight, armed, lasing with the correct code, keeping the target on the TGP, etc. Track here: https://filetransfer.io/data-package/NVeZp89g#link Many thanks.

Hello, with the Viper and a mixed payload of GBU12/GBU24 I wasn't able to release the 12's although I was on a level flight, armed, lasing, etc. I wasn't able to find what I was doing wrong, since I was able to release the 24's, although they didn't track the laser, but that's an issue for a different ticket that I'll open now. I have other squadron mates that have had the same problem with the Viper/GBU12's. Track here: https://filetransfer.io/data-package/NVeZp89g#link Another track from tonight, no mods. Min 15.00 and onwards: https://filetransfer.io/data-package/gU075zpO#link Many thanks.

I don't do anything apart from pointing with the TGP, pointing with the Mav, boresight button, switch station, boresight button, and done. It doesn't make any difference if you enable ground jettison, master arm on sim, etc. Apparently it doesn't even matter if you point the Mav a the same thing your TGP is pointing at. As long as you press that boresight button you're golden.

It's no secret that you get a lot of flak and I think that, as long as it is not rude, this is a good thing since there's no competition to DCS and you need the users to keep you from getting complacent. However the last updates, especially the last one (FLIR, CRUS, FM, Paveway III...), show that there's a lot of love for the Viper. Things like radar and weapons still need adjustment; but because we give you hell when things go sideways, I think it's only fair that we give you kudos when you do a great job. Congrats to all the team and keep it up. I'm enjoying the Viper more and more with every update.

Hi BigNewy, good evening, pinging to inquire about this as I understand it couldn't go into this update. Would it be possible to have a rough timeline? Many thanks.

Thanks, it's clear now.

I apologize beforehand if this is a recurring question, but I read the OP and searched the zip for a readme and I couldn't find anything. I downloaded Grinnelli's mod from https://www.mediafire.com/file/d75yuv540r38qr4/Community_F-22A_Mod_Version_II.zip/file. Now: Where should I install it? I assume next I need to download both Nightstorm's enhancement mods. Where should I install them? Is there anything else I need to do? Thanks everybody.

160 feels a bit too slow. I'm taking off at 190/200kts fully loaded without puncturing a tire.

Hi BN, wanted to check if this has been fixed. Just did another sortie where I was locked by the 5 but couldn't see it on the HAD. Thanks.

Did you try to also adjust contrast? Is your target on range?

Oh, this is a bummer, I had documented the bug perfectly and was looking forward to opening the ticket. Thanks for pointing me in the right direction, at least I know I wasn't day dreaming! It's funny because my TacView replay shows me crashing, yet the server's TV shows me living...

As title. I took off a couple hours ago because I wanted to document a bug with the Viper's JSOWs, I managed to launch 4 JSOWs between evading SAMs by diving; however, when I'm replaying the track it shows me crashing after launching the first one. Aren't tracks supposed to be 1:1 copies of the game? Thanks.

How do I unselect my PDLT? Not replacing it with another plane, just getting rid of it completely. Thanks.

Thanks for supporting the VR fellas! A resizable screen and the option to not be on top of everything would be most welcome for us. Thanks!!

Track here. Tacview here. Rough timeline of events: Before takeoff I set my HAD to target lists 1, 2, and 3 as I will be attacking a SAM-5. I start flying 45º into the SAM, to put it at around 20-30NM. SAM-5 targets and fires a couple times. My HAD detects the 5 tracking and slowly updates to PGM-3. Suddenly, the 5 goes cold on my HAD although my RWR has it tracking and firing. Nothing on the HAD for a long period of time although RWR keeps beeping. I change to all Threat lists, I restart the HAD, nothing... I start getting targets back on the HAD, but not the 5, although it keeps tracking and firing at me. I fire a couple HARMS to 19 and BB and they impact at PGM-2. The 5 never comes back up on my HAD.

Can you clarify this? What is the climb mach?

Please share that mission when you create it, as I also need to practice AAR. As for the case you mentioned, afterburner on the Viper is for taking off under big loads on short runways or for defending missiles. If you need it to reach any altitude it means you are overweight. Set military and a pitch of 5° and stabilize when your AoA is more than 7°. Gain speed and keep climbing until you cannot maintain Mach 0,60-0,65. That's your ceiling. On another note, I never have needed going supersonic or over any altitude to launch a HARM, (in fact I rarely go supersonic on purpose), and I'm hitting targets even when I launch them at deck altitude. As long as you are within the missile's range, you shouldn't have any problem other than the SAM site shooting your HARMs down, which is solved by attacking with JDAMs. With a centerline and going a notch below military you can have a +1h playtime fully loaded with JDAMs and 2000lb GBUs, and get back to base safely. Also, as they have mentioned, 800lbs of fuel go a really long way. In any case, the CRUS page will be very useful whenever ED launches it.

No matter how much I play with brightness and contrast I just cannot see most targets unless I'm right above them, which is useless by then. HOC and COH just changes the crosshairs color, nothing else changes. I usually target through TGP and pray that the Mavs are locking in the target, but if I have to refine I need another pass. I would be OK with the other problems as long as the PGM was fixed. What doesn't make sense is circling a SAM 3 times and still not having the Y axis dialed-in. -- I have no problem with JDAM's and JSOW's precision, but I believe the splash damage is not modeled correctly since impact from a JDAM 10 feet away results in 0% damage. The JSOW... where to being, I just threw two JSOWs onto a SAM-2 site that dropped bullseye and 0% damage again.