lancerr

Thanks Hollywood. Got past that one and then ran into the usual issue - F14B not being detected by Vaicom plugin on the PTT page. Deleted Export.lua and VAICOMPRO folders in both DCS and DCS.OpenBeta. REstarted VoiceAttack, Vaicom. Then started DCS. STill nothing.

Hollywood - Issue with AIRIO refence in manual. You state "After VA restart, new keywords will have been added to your alias database. Follow the regular FINISH steps (see page 39) to update your VA profile with the new keywords." However page 39 does not contains Finish Steps for VA profile. Searching through the doc we find 1 more reference for "Finish Steps" but no actual page for it. Thanks.

Posted in a different thread Cobra. Did you see it? Sent from my SM-N960U1 using Tapatalk

Anyone getting 40% CPU usage with SimShaker. It looks like it's causing a crash in DCS and after DCS closes, I find that SimShaker 1.3.6.11 is using a lot of CPU cycles. I have to force quit SimShaker and restart. Running it on Win10, DCS OpenBeta 2.5.4.28840, Jetseat

Can anyone explain whey there are fundamental flight model changes at this stage? Turn Rate / Acceleration / Spped bleed off are all noticeably different after this patch. I would think early access would focus on bug fixes, tuning avionics, finishing up manual. etc.

Beautiful Coxy. Awesome composition.

I set up a mission with 6 Tu142 launching the KH-31's and each plane launched something like 6 missiles - jester went nuts trying to warn me about each one. Had to have him STFU.

+1 Most of my issue with situation awareness on the tomcat seems to be because F14 is designed for the pilot to be supported by a competent RIO and it's not possible for the pilot to compensate for a bad RIO since he lacks the displays and controls the RIO has.

Hey Gents, Putting in those hours in the F14 and it's been a nice learning curve. Still have a ways to go and I have been exclusively flying as the pilot not the RIO. I'm coming from an Su27 to give you some context. I'm struggling with getting a full picture of the battlefield and I'm wondering if you folks have any tips. I've set up a mission where I launch from Stennis to intercept 2 seperate flights of Tu142 and Tu22 flying anti-ship and anti-runway missions with Mig31 and Su27 escorts. Here are my specific challenges. 1. I tell jester to auto manage radar range and azimuth. Looking at the TID from pilot cockpit, I cannot tell what settings he has chosen. The elevation is to the left on the TID but is this degrees or bars? Is Jester at 50 or 200m range? 10deg or 65deg AZ scan? It's hard to judge where I am in relation to the enemy quickly. 2. Is the radar in pulse or pulse doppler and if pulse doppler is it in TWS? 3. I can't tell the difference between bombers and fighters on the TID. On the su27 I get 4 dashes for large aircraft and two for small which makes it easier to understand whether I'm locking up fighter or bomber - how do you do that in the F14? This is assuming you are out of visual range of TCS. Any help is appreciated. Thanks,

Thank you for the profile. Question, I don't see any radar/stt lock commands or am I not looking at the right place. I see lots of radio/tacan/waypoint nav related commands. Sent from my SM-N960U1 using Tapatalk

Yup. Same here. Looks like the errors may be because of wrong sound file names Heatblur. See attached comparison between error thrown about sound files and actual sound file names. 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110rearclose): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110reardistant): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110rearclose): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110reardistant): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:01:39.041 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:01:39.595 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:01:39.595 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesider): gain 2019-03-23 18:01:39.595 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:01:39.595 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesider): gain 2019-03-23 18:01:41.683 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110afterburnerrearclose): gain 2019-03-23 18:02:05.438 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110rearclose): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110reardistant): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110rearclose): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110reardistant): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:02:05.438 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:02:05.993 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:02:05.993 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110enginesider): gain 2019-03-23 18:02:05.993 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:02:05.993 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110enginesider): gain 2019-03-23 18:02:08.075 ERROR SOUND: invalid source_params(woLA-16782336:aircrafts\engines\f110afterburnerrearclose): gain 2019-03-23 18:02:15.356 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110rearclose): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110reardistant): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110enginesider): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110rearclose): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110reardistant): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:02:15.356 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110enginesider): gain 2019-03-23 18:03:07.335 ERROR SOUND: invalid source_params(woLA-16782592:aircrafts\engines\f110afterburnerrearclose): gain 2019-03-23 18:06:24.475 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-23 18:06:24.475 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-23 18:07:03.931 INFO Lua: Lua CPU usage: metric: average mission execution: 6.2971 % 2019-03-23 18:07:42.907 INFO Lua: Lua CPU usage: metric: average mission execution: 6.9230 % 2019-03-23 18:08:29.203 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain 2019-03-23 18:08:31.833 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\windrushing): gain 2019-03-23 18:08:35.093 INFO TACVIEW.DLL: During the last 600.0s an average of 30 units objects and 4 ballistic objects have been active per frame 2019-03-23 18:08:35.093 INFO TACVIEW.DLL: The average frame rate of 80.5fps would have been 82.7fps if the flight data recorder was disabled 2019-03-23 18:08:35.093 INFO TACVIEW.DLL: DCS World simulation is taking 97.3% of CPU 2019-03-23 18:08:35.093 INFO TACVIEW.DLL: DCS GetWorldObjects is taking 2.2% of CPU 2019-03-23 18:08:35.093 INFO TACVIEW.DLL: Tacview recorder is taking 0.4% of CPU 2019-03-23 18:08:56.108 WARNING EDCORE: Source Bazar/Textures/AvionicsCommon is already mounted to the same mount /textures/. 2019-03-23 18:08:56.145 ERROR COCKPITBASE: Cockpit: can not add element 2019-03-23 18:08:56.145 ERROR COCKPITBASE: Cockpit:Parent '{CA798A73-20F9-4497-BA46-A08FB126BA12}' for '{20546C74-C84A-4e93-919E-78ED864CF39F}' is not found 2019-03-23 18:08:56.208 ERROR COCKPITBASE: Cockpit: failed to init geometry, pointer was not found. 2019-03-23 18:08:56.403 WARNING LOG: 2 duplicate message(s) skipped. 2019-03-23 18:08:56.403 INFO COCKPITBASE: lua state still active PROXY, 1 2019-03-23 18:08:56.410 WARNING F-14: F-14 Build vs DCS version mismatch! Built with: 2.5.4.28461, DCS is: 2.5.4.28615 2019-03-23 18:08:58.531 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\touchdown): gain 2019-03-23 18:08:58.531 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-23 18:08:58.531 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110intakeint_01): gain 2019-03-23 18:08:58.531 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110intakeint_02): gain 2019-03-23 18:08:58.540 INFO WORLDGENERAL: loaded from mission Scripts/World/birds.lua 2019-03-23 18:08:58.580 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\touchdown): pitch 2019-03-23 18:08:58.580 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\touchdown): gain 2019-03-23 18:08:58.580 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\touchdown): pitch 2019-03-23 18:09:00.646 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110engineint01): gain 2019-03-23 18:09:00.646 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\engines\f110engineint02): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110rearclose): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110reardistant): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesider): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110rearclose): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110reardistant): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_front_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_side_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110_rear_flyby): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesidel): gain 2019-03-23 18:09:53.766 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110enginesider): gain 2019-03-23 18:10:53.906 INFO Lua: Lua CPU usage: metric: average mission execution: 6.6693 % 2019-03-23 18:11:43.860 ERROR SOUND: invalid source_params(woLA-16782080:aircrafts\engines\f110afterburnerrearclose): gain 2019-03-23 18:11:45.019 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-23 18:11:45.019 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts\f-14\groundroll): gain 2019-03-23 18:14:37.241 INFO Lua: Lua CPU usage: metric: average mission execution: 7.2428 % 2019-03-23 18:18:35.097 INFO TACVIEW.DLL: During the last 600.0s an average of 14 units objects and 2 ballistic objects have been active per frame 2019-03-23 18:18:35.098 INFO TACVIEW.DLL: The average frame rate of 116.6fps would have been 118.8fps if the flight data recorder was disabled 2019-03-23 18:18:35.098 INFO TACVIEW.DLL: DCS World simulation is taking 98.2% of CPU 2019-03-23 18:18:35.098 INFO TACVIEW.DLL: DCS GetWorldObjects is taking 1.5% of CPU 2019-03-23 18:18:35.098 INFO TACVIEW.DLL: Tacview recorder is taking 0.3% of CPU 2019-03-23 18:28:35.104 INFO TACVIEW.DLL: During the last 600.0s an average of 0 units objects and 0 ballistic objects have been active per frame 2019-03-23 18:28:35.104 INFO TACVIEW.DLL: The average frame rate of 138.4fps would have been 138.4fps if the flight data recorder was disabled 2019-03-23 18:28:35.104 INFO TACVIEW.DLL: DCS World simulation is taking 100.0% of CPU 2019-03-23 18:28:35.104 INFO TACVIEW.DLL: DCS GetWorldObjects is taking 0.0% of CPU 2019-03-23 18:28:35.104 INFO TACVIEW.DLL: Tacview recorder is taking 0.0% of CPU 2019-03-23 18:38:35.107 INFO TACVIEW.DLL: During the last 600.0s an average of 0 units objects and 0 ballistic objects have been

Here's a better video of that same effect. Happens a lot of the time but not all the time. Not sure what triggers it.

Graphical Glitch. Captured the rapid oscillation bug that I noticed earlier. All movable surfaces + Jesters head.

Here has been my experience. Original config. Zotac Amp Extreme 1070 Ti, 32GB 3200 DDR4, 1TB Samsung 970 Pro NVME SSD, i5-8600K @ 3.6Gh, 3440 x 1440 Rog 100Hz with adaptive sync between 60Hz to 100Hz With this setup - I could not run DCS at high everything. I had to reduce MSAA to 0, Visibile Range to Med, Shadows to Medium, Ground Shadows to Flat - this resulted in about 60 -70 fps - just barely at the lower range where adaptive sync kicked in. I tried Nvidia FSAA in control panel but that didn't seem to do anything. Current Config Zotac 2080 OC'd +200 Core +800 Mem, 32GB 3200 DDR4, 1TB Samsung 970 Pro NVME SSD, i5-8600K @ 4.6Gh, 3440 x 1440 Rog 100Hz with adaptive sync between 60Hz to 100Hz. I also installed reshade and turned on SMAA. This config results in about 90 to 100+fps. Reshade is great for smoothing out the in-game visuals without a significant FPS hit but it does screw up your screenshots since they end up getting captured without the reshade anti aliasing effects.

I would love to have a running tally of how many flight hours I've put into my modules. Perhaps something stored under profile. Just like IRL. Sent from my SM-N960U1 using Tapatalk

This is not a bug. This is a really advanced multiverse feature that shows what could have happened in alternate timelines. Infinite possibilities every time you replay. Sent from my SM-N960U1 using Tapatalk

Yeah. Same here. Would love to get force feedback but the MSFT ones look dated. Sent from my SM-N960U1 using Tapatalk

This!! This was what I was hoping to learn about. Thank you for that reply. Sent from my SM-N960U1 using Tapatalk

Its unpredictable. Tried to grab a screenshot but the frequency of these oscillations are so high. I'll take a video capture tonight. I should be able to replicate it. Sent from my SM-N960U1 using Tapatalk

Not sure any one else is experiencing this - rapid oscillation of jesters head/wings/horizontal stabilizer graphically - it's like those particular ones are running at 10x the speed of the game. Jesters head swivels back and forth in high speed. Wing tips flex at high speed. Horizontal stab rapidly move up and down (like auto adjusting trim). Anyone else? Sent from my SM-N960U1 using Tapatalk

I stand corrected. Perhaps it is a modeling issue in DCS Sent from my SM-N960U1 using Tapatalk

Great discussion. Couple of points I've seen you all make. 1. F14 cockpit seems naturally laid out. Perhaps. Coming from an Su27, I think the very different design philosophies jump out at you (sort of like the iPhone vs Android debate). Once you get used to one, it feels intuitive while the other feels awkward and hard to use. 2. RWR - This one will take some getting used to. When you have information displayed in a radial form around a central point, that's a design pattern that is intuitively understood to indicate relative position and distance (Planetary orbits, Ripples in a pond,etc.). This one is just a matter of studying the RWR for a while and getting used to the display. I'm still curious why Grumman or Aircraft designers picked the current RWR layout but maybe we will never know. This is just my design curiosity speaking. 3. TID - Given Victory's comment and the comments of those using VR, this one looks like an artifact of the FOV/Projection on a flat display rather than a design issue. 4. HUD - I am getting used to the minimalist HUD but then again its supposed to be a "Heads Up Display" and I'm spending a lot more time heads down. Feels like it's missing a couple of key data points. More digging and here's what I found. F14D seems to have addressed a few of these issues. More comprehensive HUD, VDI (or more likely MFD) moved to a more logical position right of center MFD, though I can't tell what happened to RWR. Attached a bunch of images - ignore the graphics (clearly stylized) but the layout seems accurate comparing it to real world F14B and D pits.

Thank you guys for all of these interesting points. A lot of you are mentioning the same thing - that it was developed in the 60's. I did some digging and I want to run this past you in case I missed something. Some background F14 - The F-14 first flew on 21 December 1970 and made its first deployment in 1974 with the U.S. Navy aboard USS Enterprise (CVN-65), replacing the McDonnell Douglas F-4 Phantom II. (wikipedia) Su27 - "The Sukhoi design, which was altered progressively to reflect Soviet awareness of the F-15's specifications, emerged as the T-10 (Sukhoi's 10th design), which first flew on 20 May 1977." (wikipedia) I'm ignore the variants - So basically both of these planes were designed in the 60's and deployed in the 70's. One specific area that I felt was missing in F14. Lack of distance/strength of Radar threat. You all mentioned that all US aircraft are organized the same way - threat type organized around progressive concentric rings (closest least threat, furthest greatest threat) but that RWR doesn't indicate range/strength of threat. Sk000tch - you said "I don't know of any RWR that is distance based, they are all directional taking into account strength, type, whether locked or guiding, to approximate intensity of threat. You cannot measure distance based on strength and intensity, and fighters aren't large enough to triangulate. However, in the Su27, the RWR does exactly that. "In 1976, design of the SPO-15 was finished [design started in 1969], and by 1978 it was in production. This could produce warning on hostile search as well as tracking, determine type of threat and level of danger." https://www.secretprojects.co.uk/forum/index.php?topic=48.0 See attachd image - Having "relative emisison power" of threat is a huge asset to situational awareness. What I am confused by is that the Russians admitted the US were way ahead of them with regards to avionics in the documentary on Su27 development ( ). Then how is it possible that the russian su27 developed and deployed in the same time frame as the F14 has a more sophisticated and arguably easier to understand RWR than the F14? What am I missing here?

Loving the f14b. Not as steep a learning curve as I expected but very deep and Im just scratching the surface. Something that stood out. Jumping from a few other modules into F14, its remarkable how poorly laid out the cockpit (tid behind pilot stick) is, how confusing the instrument clusters (ex. speed and barometric pressure) and some highly questionable design choices (no speed indicator on HUD - really?, rwr rings that dont correspond to distance but priority). It's amazing how much worse my situational awareness is in this cockpit compared to the su27. Anyone else feel similarly or disagree? Anyone know the history behind some of these design choices? Did the design and clusters get redesigned in the D models? Sent from my SM-N960U1 using Tapatalk

This assumes that the written manual is actually well written and organized to be clear. I haven't seen yours Victory but I found the HTML starter version of the f14B not very useful. I'm sure that will improve over time. For the F14b, I find that a combination of sim time, manual study and video (quality not withstanding) to be the best way to learn for me. If i had solely relied on the manual I would be far behind where I am now.