609_Relentov

Very cool! I added 7 more song files (Song2.ogg-Song8.ogg) and it indeed played them all. I even tried the ffwd and rwnd keys and you even get the sound of the tape screech when it starts up again, nice touch :). After that the music would not play - so question, is there a way to play from the beginning again? Otherwise I presume it would take a new aircraft spawn, or at least a rearm/repair or something.

One more comment/question on the issue of establishing the QFE at a given waypoint. What if waypoints are not provided (beyond the take off airfield), and we have to add them through lola coordinates via the CK37 during the mission? These waypoints of course are not included in the generated kneeboard, and I don't recall seeing any QFE info on the F10 view. Not sure where we would get the QFE info for these, or do we just use the airfield QFE and do ballpark adjustments based on the altitude difference between the take off airfield and the target waypoint... I would imagine this could affect the accuracy (re: dispersion altitude) of the BK90.

Hmm, you're right, thanks unipus. I didn't look at the waypoint chart close enough to see that it had the QFE figures there, nice addition to the dynamic kneeboards.

As described in this thread: https://forums.eagle.ru/showthread.php?t=182425 Basically if you air-start in the Viggen, and you try to set a target waypoint (e.g. M2) fix via the radar T1 and TV keys, the waypoint circle in the radar does not move to the new position. Works OK when doing a normal ground start.

Yes, it was a target waypoint. Originally a nav point (i.e. B2), but using the CK37 I put into TAKT/input, entered 9 and then hit the B2 button and the destination changed to M2. In any case, I have an update - after I re-spawned in a ground start Viggen and went through the normal start up procedure, then changed nav point B2 to M2 and took off and tried it, it worked OK this time when I hit T1 / slew cross-hairs / TV (i.e. the waypoint circle in the radar display moved to the new position). So I think it's an air start bug of some sort. Thanks for the help, it verified things anyway :).

Good point - actually, I have been doing airstarts where this is happening. And I just realized the data cartridge isn't in (at least graphically when I look back there), although the waypoints are seemingly loaded into the CK37 as I can select them. Maybe it's an air start bug? I'll try it with a ground spawn and see what happens, thanks.

Hmm, well it still doesn't work for me. As mentioned, after hitting T1 (hat switch down), I get the cross hair, and can slew it (throttle hat switch up/down/left/right). Then I hit TV (js button) and I see the grid appear (i.e. concentric half circles with 3 lines going out from the bottom center towards the top/top-left/top-right), but the waypoint circle does not move from it's original position. Getting frustrated as I really want to try the Bk90 but I want to be able to adjust the target way point on the fly...

OK thanks guys, you're clearing things up a little, as I was a little uncertain about how to handle the three position switch mappings. I don't have a three way button, so I have mapped all three T positions to separate joystick controls (buttons or a hat position): T0 T1 TV So do I even need T0 mapped? Sounds like it should work by just hitting T1, slewing, then TV. One last question then is, do I need to hold the T1 key/button while I'm slewing the radar, then let go and press TV to bind it? Thanks...

Sorry for the obvious question, but isn't that what I just described what I was doing? Also, in the manual for an own-fix, it has T1-TV-T1, so are you saying you don't hit a T1 after?

I'm having difficulty making a position fix of a target waypoint using the radar. I watched xxJohnxx's navigation video and tried to replicate what he was doing at approximately 18:49. In my case, the T0 trigger didn't do anything, I had to hit T1 (which is also what I see in the beta manual on page 159 for doing an own-fix (i.e. T1-TV-T1), so I'm wondering if John meant T1 in his video. In any case, when I do the sequence (with the radar on, and sweeping): - T1 - Move the radar cursor to the new position - TV - T1 I suddenly see the grid lines like I see in John's video, but the waypoint circle does not move to the new location. I'm wondering if there's anything else I need to do to allow the radar to update the waypoint. I heard John say something about "if we disable editing" around 18:58; Do I have to enable editing of waypoints first via CK37 inputs? Any help would be appreciated, as without being able to fix target waypoints I would think the BK90 would be useless, among other things. Thanks, Relent

Cool, thanks grunf! Do any other DCS modules require QNF entered in mbar? If not, this sort of table would be a great addition to the Viggen manual or kneeboard, since altitude settings are so important for air-to-ground ordinance usage (and by default, DCS does not provide the proper unit of measure in the ATC call-backs). Relent

Excellent, thanks Zabuza! IMO if any DCS aircraft needs custom kneeboard images from the manual it's the Viggen! :).

I use an old MS FFB2 stick, and I was having return to center issues with Cliffs of Dover, and IL2/Battle of Stalingrad. Was driving me crazy as sometimes when firing the guns, the FFB2 stick would go limp-noodle on me, which really affected game play. I read about a small registry edit that basically turns off force feedback, but gives you return to center 100% of the time (if holding the stick normally). Ever since then, I've had never- failing return to center force, and don't really miss the lack of force feedback - works fine in the AJS-37. If you don't like it you can always undo it. Here's the tweak (I'm on Windows 7): - Open the registry editor (e.g. click the "Start" Windows icon at the left of the start bar at the bottom of the desktop and type "regedit" in the text box marked "Search programs and files"). - Navigate to the following "hive" via expanding the folders under "Computer" on the left pane: HKEY_CURRENT_USER/System/CurrentControlSet/Control/MediaProperties/PrivateProperties/ Joystick/OEM/VID_045E&PID_001B/OEMForceFeedback - Once you see the "OEMForceFeedback" folder, right-click on it and click "Permissions.." - You should see "Everyone" under the "Group or user names" - left click on it to highlight it, then under "Permissions for Everyone" click the check box under "Deny" and to the right of "Full Control" - Click OK - Close the registry editor Relent

Yes! xxJohnxx is back! Glad to see you putting up this tutorial series John - loved your work with the Mig-21. Relent

There's a similar post already, look here: https://forums.eagle.ru/showthread.php?t=181510 . I think the work around is to get in the cockpit first, then hit Esc and edit the controls, then it will work.

I sure hope not - that was part of the point of this thread. I was hoping that by using the stable install to update to open beta that all of the existing mappings would work. I'm going to make sure that I back up the DCS folder under the saved games folder just in case anything gets overwritten.

Thanks Enduro14 - I hadn't read that thread in detail but yes it covers/confirms this issue, great. @MainSail - looks like a nice tool, although I don't see myself doing more than switching between release and open beta for now so I'm good with a couple shortcuts, but thanks.

Good point, so the true test will be after tomorrow's open beta update where they would be different.. thus my initial question about if someone has already done this. I guess we'll see by tomorrow either way :). Thanks (just saw probad's edit, good deal, will give it a go tomorrow!)

Thanks probad - cool, then I'll test it out tonight as described (i.e. update to @openbeta, then back to @release, then connect to a stable release server).

Thanks renhanxue, although it would be good if someone could verify that the downgrading back to stable works OK. I guess testing would be to try and connect to a stable version in MP and if there are no issues it verifies it :). Was just hoping someone else had tried that already! ;)

While the **Viggen Release Information (27th)** thread is huge and a lot of stuff has been slung back and forth, I did want to confirm some information I read regarding updating the stable 1.5.5 release to 1.5.6 beta, and back to 1.5.5 stable. I currently have a shortcut that forces the 1.5.5 stable to update, however, I was not aware of the added parameter to be able to choose the trunk (e.g. currently 1.5.5 stable) or a branch (e.g. 1.5.6 beta), so this is cool and should help those who do not want to install a second instance of DCS. I am one of those who just has one install, DCS 1.5.5 stable, and do not wish to download the beta or alpha, as I use an SSD drive that is mostly full. And, I don't want to download another instance of DCS on my hard drive, which is why I got the SSD in the first place :). So... I currently have a short cut that forces an update, the Target value is as follows: "E:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" update If I'm reading the other thread right, if I change it to the following, it will update it to the open beta, which currently is also 1.5.5 at the moment, correct?: "E:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" update @openbeta And then if I want to go back to the stable, I can change the above (probably a different short cut) to the following, correct?: "E:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" update @release If it's as simple as that, great, as I really didn't want to have a second instance - plus all of the keyboard/joystick/throttle/rudder pedal mappings will be set (for the rest of the aircraft, etc.) and won't have to be reassigned with a second instance of DCS. As for the other thread, a lot of the disappointment is probably ill-conceived due in a lot of cases to miss-information, or lack of information (or it's hard to find). Had I known about the relatively easy method of swapping a release version of DCS to open beta with one install via update, I wouldn't have been as concerned or disappointed about this release. There's just a lot of information in the forums, and unfortunately a lot of mud-slinging back and forth when people just may not fully understand the scope of release-related issues that come up.

Yeah, I'm sort of with ruskybeaver, I was expecting a stable release version would be available. It's not the end of the world, I can wait, but I'm a little disappointed sure. I have DCS 1.5.5 stable on a 128GB SSD, and don't have room for another instance. Life goes on! :)

That would have been sweet if they could have incorporated this integrated dispenser into the AJS-37, otherwise it basically cuts by 25-50% the air-to-ground ordinance it can carry.

Thanks renhanxue, seems that having countermeasures would have been something a clean AJS-37 would have by default, but oh well :). 3xRB75 and a countermeasures pod may be a very popular loadout then (along with the two IR/Sidewinders of course) as I would think having flares/chafe will be a popular option to have going into most target areas that have IR/radar guided SAMs...

Am I reading the beta manual right in that in a clean configuration the AJS-37 carries no guns, countermeasures or ECM? So for example, if you carry 4xRB75 Mavericks on the fuselage and inner wing pylons you have no countermeasures. Do the gunpods have to be used in pairs? Would be nice if you could carry one gunpod and one countermeasures pod on the inner wing pylons, at least you could have some strafing ability and countermeasures along with the 2 air-to-ground weapons in the fuselage pylons.