San Patricio

So I've been using this mod to export my PCN to a second monitor: https://www.digitalcombatsimulator.com/en/files/2317118/ After the 2.5.1 update, I reinstalled the mod and verified that the relevant files (PCN_UR_init.lua and PCN_BR_init.lua) were in the correct directory for 2.5.1. Open Beta. The PCN no longer displays, however. I have no problem with VTB export to my other monitor but the PCN won't display. Anybody else experience anything similar?

I'll second this bit on the sounds. Not sure I ever figured out the pattern, but flying the Viggen in 2.5 I've had sounds cut in and out exactly as described above. I've also had some odd results with the TILS in the Caucasus map and the course indicator getting stuck or pinned but I haven't sat down to document them or sort out whether it's me or the system that's at fault.

There is material on the TPOD in the Pocket Guide. Also see this:

Really enjoying this campaign! One quick question: the target QFE listed on the flight data card (in the DOCS folder for this campaign) never seems to match with the QFE listed for the target on the Viggen kneeboard. I've been using the QFE from the kneeboard and that seems to work, but I'm wondering what's going on with the difference between the two.

Well that video convinces me that the sighting is working correctly, though I still consistently go long with my shots. I'll experiment with steeper dive angles. I'm wondering if maybe it's an issue that when pressing the trigger I move the stick a little and thus pitch up.

Interesting! I'm also enjoying the campaign but was repeatedly unable to hit the target in mission 3 so I setup my own test mission (2.5 OB) with unlimited ammo. Even there with repeated runs on the target I had similar issues with the rockets going long at a variety of different dive angles. It may well be I just need more practice (rockets are hard, particularly with the Viggen's pre-CCIP sight) but I know the devs said there was an issue with rockets in 2.2/1.5.8 so I'm trying to figure out how much is me and how much, if any, is a bug. I just used the same mission template and tried DYK bombing and also had it go long but again hard to tell if that's something that changed in 2.5 (I used to be pretty good with bombs, but again, they take a lot of practice) or not. EDIT: I did set the QFE for the target, though that shouldn't make big difference since both rockets and DYK use the radar ranging (my understanding is that the QFE in those cases may affect the "dot" which shows initial target location in ANF but that the actual firing indications are determined by the radar and not the QFE).

So prior to 2.5 the Viggen rockets seemed to always fall a little short following standard procedures (target motion off, wait for wings to fire). I recall one of the devs saying this was a known issue and they were working on a fix. I could get the rockets to hit consistently by aiming a little past the target point or waiting until very late to fire (the flashing side bars). In 2.5, I seem to be having the opposite problem: they almost always seem to go long. Radar ANF, aim at target, unsafe, wait for wings and fire almost invariable ends up with the rockets going long for me now. I'm curious about other peoples experience with the ARAKs in 2.5.

Bumping this because I'm having the same problem in 2.5 with missing maps for NNTR and Normandy. Also had it with 2.2. In addition, the Viggen is the one plane that doesn't seem to play well with the Kneeboard Builder app right now (not that that's necessarily Heatblur's problem).

I'm having an odd problem with Tacview in DCS 2.2. I downloaded the 1.7.0 betabeta to get around the current issues with 1.5.8 and 2.2 and it now records fine in 1.5.8. But in 2.2 it always records very small (1 or 2kb) files that contain no units and no flight data, just the selected map (this is all in single player). I did recently move my 2.2 install to a new drive, but I'm not sure what else it could be that's causing it to work fine 1.5.8 but to have this particular problem of small, mostly blank ACMI files in 2.2.

Doh. Sorry about that. Yes, it happens in missions too. Here's a track with the same problem from the Black Sea ramp start free flight mission. EDIT: Now it's actually working. I think I might have just been reading the panel wrong. Been learning BMS the last couple weeks and I think just got used to the F-16 MFD/DTC sequence. Sorry! DTS_no_load_mission.rar

I've attached a track. I went back to the BFT campaign, which is where the problem first started. I've tried a repair (non-Steam), but the issues is still happening. DTS_no_load.rar

I've suddenly encountered a weird bug where my DTS will no longer load properly in the latest stable release. It's worked fine up to today during ramp starts (which I've done hundreds of times). Suddenly, however, when trying to load it just hung and then returned to the load screen. At first I thought I messed something up in my startup, but I repeated it several times in two campaign missions (BFT and Enemy Within). Tried rebooting just in case and it always seems to have in the same place. I'm using the same startup routine I've always employed so I'm not sure what's up. Any suggestions?

Thanks for the advice and the awesome profiles. The problem I keep running into is that I am using two smaller 8" monitors. I can load the profile onto one of them and everything works fine with resizing, etc. But when I try to copy any instruments over to the second smaller panel, no data registers from the sim in game. I apologize for what is likely a silly question, but I've read the Helios manual now and watched several videos but can't figure out what I'm doing wrong. It was my understanding that highlighting an instrument, copying it, and then pasting it into another monitor on the same profile should work.

Is there a way to cut and paste individual instruments from this profile to fit on a smaller display? I'm using an 8" Liliput and while I can get the profile to work, it's too small to be much use at that size. I can highlight and copy the relevant instruments (VVI, etc.) in the profile editor to a new profile with no problem, but once copied they no longer register the data from the sim. I'm clearly missing a step somewhere but the couple videos I watched haven't helped me out.

By monitor config file, do you mean the one in Config/MonitorSetup? I tried adding the Nadir to the file I use there for my two 8'" Liliputs but it doesn't seem to be working. Do I need to add the port in the ViewportHandling.lua as well?

Can I ask what you edited to get the English language Abris and Ekran back?

I have a used MS Sidewinder 2 but I am having trouble getting the FFB to work in DCS. The stick shows up in Windows 10 and I can calibrate it. It also shows up in DCS World and works fine as a regular stick. The FFB, however, simply doesn't seem to be working when I try to use it as a trimmer in the UH-1 or Ka-50. I have the FFB box checked in the DCS settings and I tried "swap axis" in the FFB tuning box after reading the forums for suggestions. I tried using simFFB but when I launch it says "No FFB joystick found." Oddly, though, the Sidewinder then shows up in the dropdown box of available sticks. Anybody have any suggestions? Thanks!

Thanks! So it's supposed to be autoexec.lua? The readme file in the config directory says it should be autoexec.cfg.

I've noticed an issue with some missions, including weapons training in the Ka-50, where ground units and ships seems to not appear where they are supposed to be. In some cases, this seems linked to zoom as I was noticing that ship models would wink in and out of existence when I tried to zoom view. In the Ka-50 weapons training scenario, none of the targets appear on the runway at all. I tried making a scenario myself and placed ground units and they showed up with no problems, so I'm not sure what's going on here.

Neither of my main installs (beta or main branch) has the graphic.cfg. Instead, they have the .lua file an a readme that says: "Old graphics.cfg is gone and replaced with graphics.lua. However, please, do not edit this file directly. Otherwise you'll lose your changes after each update." I tried following the instructions to create an autoexec.cfg capping fps at 120 (as an experiment) and then placed it in the config directory of the saved game file for the beta (as they suggest). Still capped at 60. Could someone post a working autoexec.cfg so I can see if I'm doing it wrong?

Hmmm. . . . I can't find an autoexec.cfg file in the saved game directory for either DCS or the Open Beta. There are some .cfg files if the Config subdirectory of the saved game location as well as in the main install, but I can't seem to find this file. This is an installation over an existing open beta install.

Same problem here with FPS locked at 60. GTX 980 in Windows 10 with an i7. Doesn't seem to be happening in other games.

Has anybody tried using Crosswinds or the FFB2 with Win 10? I've upgraded my laptop with no problem, but am reluctant to move my main machine until I know both with work in terms of drivers.

Serial#: 0582 Location: Richmond, California, United States

Thanks all for the interesting responses and stories. I actually found something on this in the Army UH-1H/V manual: http://hoiquanphidung.com/tailieu/Bell-UH1H-Flight-Manual.Stamped.pdf In section 8-33, it offers advice on heavily-loaded takeoffs. You can read for yourself, but in sum it does suggest that operators can increase "beep" on the governor with the GOV INCR switch in order to maintain rotor RPM during a heavily loaded takeoff. This is, to my understanding, something done with the GOV still set to auto and is not the same as the procedure suggested in the UN campaign missions (which involves flipping the GOV to emergency).