609_Relentov

Yes, one tends to fly low in the Viggen :). I must have missed that explanation in a previous update - new feature? Thanks

Anyone else having issues with the Collimator sight for the Maverick flashing after arming the weapon and trying to slew to a target? I was flying the Viggen tonight after a long break to get some practice, and I noticed the sight was acting strange. First was this flashing... seemed OK at first, after switching the armament panel to the RB75 position, master mode in NAV (also tried it in ANF). Once I armed the weapon and started slewing, the sight started flashing continuously. I could slew and lock, but it was very distracting. Next odd thing was that the sight would stay flashing even after I flicked the cover to safe mode. Only after I rotated the armament dial did the sight go dark. After rotating back to RB75, it seemed OK for a few seconds, then once I armed the weapon and started slewing the same thing happened. My NVidia drivers are fairly recent, so it shouldn't be that... just wondering if this is a known issue. I'm using open beta, and I just applied the latest update today.

OK, back to report that the problem was apparently the F-5E driver :). I ended up dropping from a little farther out, a little higher, and level with speed closer to the 300IAS recommended, and was more successful. I think the GBU seeker just likes to start out more level and farther away than I was dropping - when it then started to nose over, it appeared to pick up the laser more consistently and start gyrating to correct. So, all is good apparently :). Thanks...

Hmm, I've been dropping at ~20k feet, so even with the altitude of Las Vegas (near where I'm dropping), the ASL would be ~18k feet. I don't know if that would have much of an effect - also I've dropped from even higher (~22k feet) with the same result. Based on the F-5E manual, the parameters for 20k feet are as follows: ≈Dmin nm/km: 4/7 ≈Dmax nm/km: 6,5/12 IAS: 300 So maybe I'm too close to the target. Still, seems odd as I'm doing the same sort of approach in Caucasus, and I've certainly dropped from lower than 20,000, and the GBU has rarely dropped dumb. Have you tried dropping GBU-12's in Nevada with the F-5E? Have you had this problem at all? Anyone? I've also tried with the F/A-18C and M-2000C and the GBU's have tracked OK with similar drop altitudes and distances as what I was doing with the F-5E. In any case, I'll go higher (in Nevada) with the F-5E and see how it goes. Thanks.

I've been flying the F-5E lately, practicing dropping GBU-12s using AI JTAC vehicles (HMMWV TOW). On Caucasus, the GBU-12s have been tracking the laser ok, guiding to target vehicles without issues. However, on the Nevada map, it seems that most of the time the GBU-12s have been going dumb immediately after release and not hitting anywhere near the target vehicles. Seems that maybe 1 in 20 drops have the GBU-12 tracking the laser and guiding to the target vehicle(s). Is there anything different in the process of dropping GBU-12s using an AI JTAC in Nevada than in the Caucasus map? I've done the same thing in both, calling up the JTAC vehicle, getting the tasking, 9-line, IP-Inbound, Laser On, SPOT, IN, getting Cleared hot... having prevoiusly turned on the external stores to BOMB, bombs arm to NOSE & TAIL, selecting the proper pylon, ensuring the select jettison is off. I generally drop from ~20k feet (the practice mission has manpads/IR SAMs), with a slight dive towards the target, 250-300 IAS. As mentioned, in the Caucasus map mission, the bomb tracks right after release, but in Nevada it rarely does. Before diving in and making a simple Nevada mission so I can try and create a small track and post in the bugs forum, I'm just wondering if anyone else is having issues getting the GBU-12s to track an AI JTAC provided laser in the F-5E in Nevada. EDIT - I'm using the default laser code of 1688 (checked the kneeboard), and that is the code the JTAC is mentioning in the 9-line, so I know the laser code is correct. Thanks...

I’ve only used CCIP mode to drop GBUs in the F/A-18C, I haven’t tried auto yet. Once I get the “cleared hot”, I throttle back from > 20-25k and dive in w/CCIP to drop in the general area of the target, then pull up to avoid any IR SAMs.

+1 Needed more and more, for M-2000C, F/A-18C INS alignment, or adding waypoints for the F/A-18C, etc

Not sure if this will help, but wanted to share in case you’re having the same issue I had. Recently I changed the page file from a secondary drive it was on to a larger C: SSD. However, I had allocated a fixed size page file. Unbeknownst to me, DCS apparently didn’t like this, because I noticed that I was getting basically a black screen (except for the status bar at the bottom) when I joined multiplayer servers like blue flag. Then I had to kill DCS via task manager, etc. A squad buddy had a similar issue and had me change the page file back to Windows (10) controlled (I.e. size). After that, and a reboot, all was well and I could connect again no problems. So, the question to you is, have you changed your page file configuration lately?

Wheelyjoe has created a "Chuck's-like" manual, posted in another thread, that is very good: https://forums.eagle.ru/showpost.php?p=3695827&postcount=42 heclak is also working on a manual, posted that same thread, that is also very good (still WIP): https://forums.eagle.ru/showpost.php?p=3694010&postcount=26

Another guide, excellent! Thanks for the effort.

I had these as well but applying the hot fix from yesterday (scroll up a few pages) fixed the issue for me.

Which lights? For the cockpit (gauges, etc), there are two knobs on the right side console toward the back that if you rotate will turn on the cockpit interior lights. I haven’t been able to turn on the external nav lights yet, but the AI has them on so I’m sure I’ll find it :). The interior lights can be turned on even before requesting external ground electrical power.

I was given this link to post bugs: https://goo.gl/forms/lmpuKQCH8S8QlH0R2

Great start heclak - much appreciated!

Excellent, thanks Merker! I was thinking of submitting another bug report as I was seeing the strange white/somewhat opaque canopy glare as well, hard to see anything through it. Glad you got it fixed already... just applied the hotfix and the glare is gone, so I/we appreciate your quick turnaround on that fix!

Thanks for the quick update Merker and team! Much appreciated. Glad you got it started. My bad from my previous post, it was from memory... I mistakenly thought the APC was the APU.. so ignore that :). The key, as you saw, is ground electrical power, right clicking once on the throttle to get it to the idle detent, hitting the start button, then right clicking again on the throttle to depress it after the engine has spooled up to > 10-15% or so...

Works for me Ram - I had to use a key mapping (h in my case) as the mappings for other devices were disabled.

I had noticed this (guns) too, the log/score (‘ key) showed hits by 7.62mm after a test flight last night. I’ve submitted a bug via the bug submitter form for this so hopefully they’ll fix it. Assuming you tweaked a lua file - care to share the file and fix? :) Thanks..

There is no current alpha version anymore., maybe when the readme instructions were originally written, openalpha was still current. Thus, while the readme has instructions to install to “DCS.openalpha”, replace that part of the path with “DCS” or “DCS.openbeta”, depending on what you have installed..

Make sure you ask the ground crew to turn on the electrical power. After that, you can then turn on the APU in front of the throttle (and I think flip the switch next to the APU - going from memory here, not at my PC), and hit the start button. After the APU/engine starts spooling up, you need to depress the throttle (left click I think), and the engine should spool up at a higher rate on its own power. Then you can turn off the APU and have the ground crew turn off the electrical power. Probably more than you needed but wanted to be thorough :) Have fun.

Thanks Jaster, submitted the defect. I didn't see a way to attach an image, but hopefully my description is enough.

@Merker - A-4E-C Mod - Bug report thread? Once again, fantastic work on the A-4E, very fun to fly. Will there be an area to report bugs? Not sure what sort of plans there are to fix anything, if any. However, I figured I'd start here :). One thing I noticed is that the 20mm didn't seem to do much damage. I flew in offline mode and I may have figured out why. When I looked at the log/score (' key), it shows that weapon being used is "coltMk12", and when I got hits on the enemy aircraft, it shows "7.62mm". So I'm wondering if somehow the specs for the 20mm were inadvertently set to a light machine gun round instead. It would certainly explain the lack of "punch" of the 20mm :). Thanks in advance for looking into this. Relent Added an image showing the gun info seen from the log:

Excellent work team! Thanks for all of your collective efforts to bring this module to life in DCS - much appreciated! Similar situation.. from the readme: I was thinking the DCS.openalpha was to be replaced with whatever version of DCS you are using. However, I did try it as described in the readme, but I could then not find this aircraft anywhere in DCS (main screen, instant action, mission editor, etc.). From there, I instead added a Mods\aircraft folder structure under my current/only DCS version - e.g. C:\Users\YOURUSERNAME\Saved Games\DCS.openbeta\Mods\aircraft - and I was able to see the mod in the main screen, instant action, mission editor, etc. After that I tried to join the Blue Flag Caucasus server, and I was happy to see that it passed the integrity check, as I was able to join and jump into an AV8B/NA.

Very well said Zhukov.

Top, that’s me, Relent :). When I made an account I was in 609 squadron, and I was not able to change my ED account name, so it stuck :). So yes its the same issue - we haven’t been able to find the culprit that causes the endless beeping. However, since you can host other missions in MP and not get the beeping in FC aircraft (as the host), there’s something about the mission that’s causing some sort of conflict, still unknown.