thetford569

Sent you a PM with my interest and a couple of questions. Thanks!

I'm having an issue where Open VR Kneeboard moves positions every time I load into DCS and also during flight. I've never had this problem and been using it for months. I keep having to go in and adjust the kneeboard position every time. Any suggestions?

Follow up after I started thinking about this error....solution for me was to Install the DCS Huey module which I had uninstalled. Once I did Kneeboard Builder now works fine.

I have been getting a slightly different error message after the latest patch: --------------------------- The developer must be a moron because there was an error! --------------------------- Use Ctrl + C to copy this error and e-mail it to s13solutions@gmail.com : System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\thetf\Saved Games\Mods\aircraft'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator`1.CommonInit() at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost) at System.IO.DirectoryInfo.EnumerateFiles(String searchPattern, SearchOption searchOption) at KneeboardBuilder.Viewmodels.MainViewModel.FindLuaFile(String _pathToSearch, String _fileNameToFind, String _aircraftName, String _optParam) at KneeboardBuilder.Viewmodels.MainViewModel.GetDeviceInitPath(String _dcsPath, String _dcsSavedGamePath, String _aircraftName) at KneeboardBuilder.Viewmodels.MainViewModel.SetupKneeboard(String _dcsPath, String _dcsSavedGamesPath, String aircraftname, ProfileModel _selectedProfile) at KneeboardBuilder.Viewmodels.MainViewModel.UpdateDefaultKneeboards() at KneeboardBuilder.Viewmodels.MainViewModel..ctor() at KneeboardBuilder.Views.MainView..ctor() --------------------------- OK ---------------------------

I just came here to check because I am getting the same error.

I had some FPS Issues with the 476th NTTR Missions as well. Make sure if you are running TacView that it's turned off and not recording. The large FPS drops that I had were due to TacView running. Once I disabled it in the menu in the DCS Settings FPS returned to normal. I did still have to use either the 60s or 70s mission as the mission including all the ranges was still too much of a hit. But now it's running fine in VR and I have an i7 7700k with a GTX1080. Brandon

Amen!

Thanks!

Using the latest Open Beta and still only getting numbers for the callsign in the Hornet. Tactical callsigns should be used during the mission with MODEX (side) numbers only used around the boat. Right now it's using a 3 digit number for everything. Hopefully this can be fixed...it's difficult to tell in the mission when I am supposed to be Colt 1-1 when radio calls are made.

Ugh are you kidding me?! I missed this on sale I guess as it now says $449 at Wal-Mart?! Was this only for a day?

The JTAC in the Nevada mission is getting killed at some point after starting the mission. So if you are quick on the radio you will get the first call and then he won't be available anymore. If you wait to try and call him the first time he won't be there because he's dead. I edited the mission to make the JTAC invisible following some directions in this forum and then saved a customized mission with that setting. That's the only fix right now until ED can change their mission to keep the JTAC from dying. Brandon

Just confirming that I have flown enough now to see this as an issue. Hopefully it's just temporary. The side numbers are used for operations around the boat but the tactical callsigns (Enfield, Colt, etc.) should still be used elsewhere during the missions. Maybe they're still figuring out how to use both with the new carrier communications. Brandon

I have flown this mission twice and I am seeing the same problem as you. First LGB drop goes fine and then I can’t get past the 9 line readback menu. JTAC says readback correct but the menu never changes. I tried reading back about 10 times and it never changed. So I just went and tried to splash the Migs and headed home. Fired my 2 AIM-120s inside of 20nm and both missed which I saw in another thread that AMRAAMs are having tracking issues in the latest Open Beta which is what I am flying. Brandon

The Navy uses numerical callsigns around the boat but the tactical callsigns should be used elsewhere. I believe I have been seeing this same issue as the original poster described however I haven’t flown enough with talking on the radios to notice it as I’ve been doing a lot of training missions in the Hornet as a new DCS pilot. Anyway the tactical callsigns should still be used and if they aren’t then there is a problem.

It’s been working fine for me since the last patch