overalien

here you are. SLI-Specific changes from default blank profile linked to dcs.exe are in red.

Hi Home Fries Firstly, I love your script - it is one of the best and most well thought through tools I have experienced for DCS. I can't imagine not using it if you have a Warthog or Cougar... great work, man!!! The support and documentation and all the effort you put in are just epic!!! I use VAICOM Pro with Easy Comms off for the A-10C and have set up 'Force Comm State On' for VAICOM Pro in CTS to keep as a backup in case i quickly need to select something in a comms menu via F keys. It seems to me that the 'forced on' comm state with hats working as F keys works for a while, but at some stage is deactivated in the script during a mission... The radio PTT buttons still work properly in VAICOM, but the hats no longer work as F-Keys while the radio button is held. Have you observed this behaviour or can you think of a reason why it might be developing over time during use in a mission? EDIT: Forgot to add that I have 'SRS' activated in the script options as well and use SRS in combo with VAICOM in MP..... could it be that this is a setting which causes inherent conflicts regarding the Radio Button functionality with Comm State?

I use a special DCS Profile created with NV Inspector (I deleted the default NVidia Profile for DCS). The new profile is a simple setting change - SLI Compatibility Bit for DX10 set for 'World of Tanks'. Leave the rest of the SLI settings at default. You can verify whether it works by switching on the SLI indicator or by monitoring that BOTH GPUs are at near 100% utilization with a better framerate. I am not at my computer right now, but see if you come right with that. Otherwise I will try to upload my NV Inspector Profile in some way.

looks like the latest OB updates fixed all cloud flickering in SLI. Can anyone else confirm? Flickering for me is gone since the update from last Friday!

Thanks Hollywood. Working great so far and the bug looks fixed. Thanks so much! Sent from my iPhone using Tapatalk

Same here. Rolled back to previous and did manual .lua install and all except automatic chatter works again. Seems current version has a bug. Sent from my iPhone using Tapatalk

Hey Hollywood Firstly I"d lake to say thanks for a really great and well thought-through app!! Many KUDOs to you. I have been flying the Hog for many years and and just discovered that using VAICOM really reduces useless workload and increases immersion dramatically! I am new to VAICOM and your new Menu-Independent interface to DCS. All is working great on my side so far but I cannot figure how to command to any of my Wingmen to "engage ground targets at my SPI, with <OPTIONAL WEAPON> and <OPTIONAL DIRECTION>". Is this possible with your current 2.5.4 keyword set? I tried "D-Link Target(s)" with SPI Broadcast set to ON, but the Wingmen consistently respond with "Unable". May be a DCS Bug or I am using the command incorrectly.... Can you give me a tip please?

Bump Sent from my iPhone using Tapatalk

Dear ED team Thank you for a great sim and all the work going into the new models. You guys are doing an awesome job. Some of the basics need attention however and this bug is a real problem, especially for those enthusiasts who invested in high end hardware. Could you please at least acknowledge that the issue is reported and receiving attention? Sent from my iPhone using Tapatalk

It’s a bug that has been reported. Sent from my iPhone using Tapatalk

.... bump Sent from my iPhone using Tapatalk

I think i read somewhere that all the new modules come with their own view settings in their own dedicated files in the game install folders. Nothing you do in Snapviews.lua or Server.lua in your Saved Games can override this apparently. This is not specific to the FA-18C and might also not change once early release ends..... I hope ED reconsiders and integrates the new modules into the existing structure. that worked well for all, IMO.

Hey Guys I made some tweaks to the FA-18C Views.lua file which work better for me on a triple monitor setup and TIR This places the pilot head slightly back and corrects the default view angle to place the velocity vector more to the screen centre. You have to glance down to see your gauges but this just feels more natural. Useful maybe if you want to give it a try. Code is here: ViewSettings = { Cockpit = { [1] = {-- player slot 1 CameraViewAngleLimits = {50.000000,190.000000}, --****** set FOV default at 120 (was 20,140) CockpitLocalPoint = {3.533,1.156,0.0}, CameraAngleRestriction = {false,90.000000,0.500000}, CameraAngleLimits = {200,-90.000000,90.000000}, EyePoint = {0.05000,0.100000,0.00000}, ShoulderSize = 0.25, Allow360rotation = false, limits_6DOF = {x = {-0.18,0.30},y ={-0.3,0.2},z = {-0.18,0.18},roll = 90.000000}, -- def {x = {-0.13,0.30},y ={-0.3,0.065},z = {-0.18,0.18},roll = 90.000000}, }, }, -- Cockpit Chase = { LocalPoint = {-5.0,1.0,3.0}, AnglesDefault = {0.000000,0.000000}, }, -- Chase Arcade = { LocalPoint = {-21.500000,5.618000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } local function head_pos_default(tab) if not tab then tab = {} end tab.viewAngle = tab.viewAngle or 63 tab.hAngle = tab.hAngle or 0 tab.vAngle = tab.vAngle or -5.5 -- -9 -- -2 -- ***def (whole line) was: tab.vAngle = tab.vAngle or -15.7 -- -9 -- -2 tab.x_trans = tab.x_trans or 0.13 --0.0592 tab.y_trans = tab.y_trans or -0.0083 --0.0072 tab.z_trans = tab.z_trans or 0 tab.rollAngle = tab.rollAngle or 0 return tab end

Trying to use my standard working settings for export of MFCDs to separate monitors with the FA-18 causes the MDI displays to not display at all - neither in the cockpit nor on the separate monitors. With A-10C this still works 100% after the update. I tried various hacks of the lua scripts using older methods but the best I could get was MDI content being repeated in the main display window. But, this only happened if the Monitor setup file has the MFCD Export lines removed completely... strange.... and not really a usable export :( Anyone have any ideas or might this be a bug?

Can anyone help me with changing a setting to receive datalink messages (RCVD MSG Screen) in MGRS coordinates for the target location instead of what appears to me default LongLat coordinates? Beacuse of the current Datalink bug on 2.5.2, I am relying on this info to double check my manual entries into the CDU for target location.

I think after the latest OB update from this week the Datalink is not fully fixed yet. JTAC interaction now seems OK, but the targets do not appear on the TAD for A-10C (no red triangle) after "stand by data, cleared to engage" response by the JTAC. Can ED re-report this please?

has anyone found a new workaround ? I'm about to bash keyboard with head...

I have flickering of cloud shadows dancing in random blotches on the ground over lit areas - this happens when flying a night (dawn) mission. (2.5.2. OB Persian Gulf Map) - anyone else have this or know how to fix? My Rig is running SLI with the STALKER compat BIT and forced AFR2. It is unlplayable at night in lit areas on the new Persian Gulf Map.

I have flickering of cloud shadows dancing in random blotches on the ground over lit areas - this happens when flying a night (dawn) mission. (2.5.2. OB Persian Gulf Map) - anyone else have this or know how to fix? My Rig is running SLI with the STALKER compat BIT and forced AFR2. It is unlplayable at night in lit areas on the new Persian Gulf Map. *EDIT: and at daytime clouds are flickering no matter what settings or SLi BIT I try.....

Not sure if related, but in SP at night the runway lights appear and disappear depending on angle and position of approach. with the currently already too dark lighting at night, this is making landings very 'intuitive' :p

This issue seems intermittent. sometimes the triangle appears and sometimes not - in similar missions.

I think after the latest OB update from this week the Datalink is not fully fixed yet. JTAC interaction now seems OK, but the targets do not appear on the TAD (no red triangle) after "stand by data, cleared to engage" response by the JTAC. Anyone else have this issue?

nope the process in this case is as it should be. in-task with the same JTAC and the same target.

Hey guys. anyone have this issue in 2.5.1 OpenBeta? the JTAC Dialogue stops working at the 9-Line Readback - hitting F1 does nothing - no readback and no further interaction with the JTAC. Checking out and checking in again with the JTAC also makes no difference - you are just stuck there.

Looks like the issue is being addressed: https://forums.eagle.ru/showthread.php?t=205755&page=2