Tetra

Gotcha, thanks both of you, good to know it's just a result of Viacom. Appreciate the input.

Should be plug and play aside from binding the buttons in DCS. Only thing I can think of aside from what MustangSally mentioned above is did you ensure the export.lua is being generated? I know in the past with just the F16Ex stick I have disabled this, but the ICP needs SimAppPro to have the lua export enabled to allow the ICP to mirror the game output and naturally SimAppPro needs to be running in the background too while you play.

Saving and replaying a track file of an AAR session will not show any radio comms performed or trigger the tanker to drop the boom. Branch: Open Beta Build: 2.9.2:49940 Mission: Aerial Refueling F16 Instant Action - Caucasus Jet: F16 Issue: Contacted tanker (using Voice Attack + Vaicom Pro), Opened fuel door, set HUD to show data and ICP to bingo page. Approach tanker, contact tanker, ready pre-contact, perform full refuel, no disconnects. Disconnect on transfer complete and fly off. Save the replay, load the replay, however no radio contact with the tanker is shown, not approaching to refuel, or ready-pre contact, therefore in the replay the tanker boom never drops to refuel. All the replay shows is me flying along behind the tanker with no boom connected to the jet and no fuel being transfered. AAR_F16_Replay_Bug.trk

Yeah I guess in that situation the frame rate isn't helping much and it's the reduction in resolution data (as the planes are at a greater distance from you) instead. I guess higher frame speeds are more noticable in the cockpit, for example the F18/F16 mfds or the fuel rate indicator on the F16 when throttling up and down.

Another huge element that contributes to the ghosting effect (aside from ensuring there is sufficient resolution data to calculate from) is your fps. Probably not so much of an issue for pancake players, however in VR utilizing DLAA or DLSS without sufficiently high frame speed, for example with ASW or SSW on, exacerbates the issue greatly. It's highly noticeable say at 36/45 fps when ASW kicks in vs 72 or 90 fps, where it's a lot more subtle.

There is also another way around the CTD issue and that is to enable the VR controllers in the DCS VR menu. For some reason while they are enabled turbo mode won't CTD when enabling or disabling it. So you can toggle them on, make the change to turbo mode, then toggle the controllers off again after.

Would be caused by DLAA, ghosting is still present with DLAA, but can be lessened with increase to pixel density.

Personally use this JoystickGremlin plugin I found a script for somewhere on the net (can't remember where to credit the original poster sadly). Just modified it slightly to recenter the mouse just below center. Save it as a python file (*.py) and load it into JoystickGremlin user plugin section and bind a hotas button to recenter. import gremlin from gremlin.user_plugin import * def centerMouse(): import ctypes import win32api import win32con user32 = ctypes.windll.user32 # Get the screen resolution screen_width = user32.GetSystemMetrics(win32con.SM_CXSCREEN) screen_height = user32.GetSystemMetrics(win32con.SM_CYSCREEN) # Calculate the center position center_x = screen_width // 2 center_y = screen_height // 2 # Set the cursor position to the center then add offset to lower it (+47 is just below eye center) win32api.SetCursorPos((center_x, center_y + 47)) print("Event executed!") mode = ModeVariable( "Mode", "The mode to use for this mapping" ) btn_1 = PhysicalInputVariable( "Button", "hit the button", [gremlin.common.InputType.JoystickButton] ) state = [0, 0] decorator_1 = btn_1.create_decorator(mode.value) @decorator_1.button(btn_1.input_id) def button_1(event): state[1] = 1 if event.is_pressed else 0 centerMouse() # Call the centerMouse function here

Still trying to get it right, but the smoothest one I've managed so far, although touched down way too early and probably a bit slow (couldn't keep the nose up for very long here)

Thanks, Raptor, that makes a lot of sense, much appreciated! Also Vortex, I was encountering the same today too, have been following the manual/youtube/kneeboard procedures on this and was unable to mimic having to press TMS to ground stabilize, was also having some issues being able to then refine the HMCS SPI point with the RDR cursor slew as well, seem unable to slew inside the HMCS sights, however, I'm also relatively new to the F-16 so I could well be doing something wrong my end.

I think I know the answer to this already, but just wanted to be absolutley sure. Am I correct in assuming that there is no way of having the TGP slave to a SPI created by the HMCS ? VIS and DTOS mode weapons will slave automatically, but the TGP cannot be slaved to the SPI without going through the route of: using the HMCS to create a mark point -> assigning that markpoint as active steerpoint -> slaving the TGP to the newly active steerpoint. Thanks for any help!

Negative G's, the Mig does not like them at all. Engine shutdown is the immediate side-effect.

There is a bug with the ARC needle where it does not rotate after passing the station, it will continue to point in the same direction unless you either cycle ARC channels or turn 45 degrees away from it then back again. It's been reported but didn't make it in to the previous patch.

Fix is here > http://forums.eagle.ru/showpost.php?p=2207115&postcount=8

Skulleader I have added a fix in uboats thread for you guys.