-
Posts
215 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Yes, I had them both active. And the result of both being active causes this issue. The reason I had this set was because I had a "sticky" enabled for spring force saturation. You can not have any "sticky" enabled and get force trim feedback from DCS. I have learned you should not have hardware force trim active in VPForce configurator or have any "sticky" active while using the DCS Apache and TelemFFB. Use the DCS trim binds only.
-
I have had the Apache from day one and have 2000+ hours flying with this module. I have a non FFB stick (Virpil Alpha stick, Virpil TMC2, TMC3 bases) flying for more half of the time. I also have the Rhino FFB. I do want to detail the effects that I am experiencing. I also have the ability to test both a standard stick and base and I also have a Rhino FFB. But, for now, I'll share what I see with the Rhino FFB ecosystem. When using the Rhino FFB and CYCLIC TRIMMER MODE - INSTANT TRIM (FFB FRIENDLY), I have TelemFFB running with many of the effects turned on. In the VPForce FFB config software, I have hardware force trim checked and have the force trim bound to the same button as the DCS binding. Having TelemFFB off, the result is NOT the same. What is demonstrated in the video (Trimrelease.mp4) is me holding the DCS control binding - Force Trim/Hold Mode Switch - R/Up, then releasing it. You can see when I release the force trim the aircraft either rolls left or right and pitches up or down. It's enough of an effect to severely affect stability. While I am pressing and releasing the force trim, I am holding the physical stick position in the exact same spot when released and depressed. I do make minor flight adjustments when holding the force trim in parts of the video. I do believe there is an issue with the TeleFFB that causes this. Could it be the force trim button bound to the same key? I am not sure. Trimrelase.mp4 https://drive.google.com/file/d/1d2nlpAXvApaiBLlqpaMfoFC8hfZC-gNq/view?usp=sharing
-
Carrier operations not working as it should
JIGGAwest replied to gunterlund's topic in Multiplayer Bugs
A few of us seen the same exact thing in multiplayer. The patch notes mention possible issues with slot switching while operations active. I believe we had 8 people trying things at the same time. I'm pretty sure we had a spawn issue and two aircraft caught fire. We couldn't get it to work much after this. we were using dynamic spawns. Have not tried with traditional spawn placements. -
When using a dynamic slot on a dcs multiplayer server, If you change pages in the kneeboard, DCS will crash. see attached track file Wolf_pack_U.S._Nevada_Red_Dawn_V-2.4.0.29-20240810-110902.trk
-
I never would have assumed files from the stand alone server were the same as the client. Additionally the server wasn't updated yet, so I'm not sure why it would need to copy files from an older version. Everything seems to work fine, I was worried the version merge was choosing the wrong install.... no no not the server!!!
-
I am seeing something that concerns me. I am running the DCS updater for the open beta client install and the updater is coping files from my open beta server. why would it need to do that? my saved games folder structure for the open beta client is c:\ users \ username \ saved games \ DCS folder for the open beta server is c:\ users \ username \ saved games \ DCS.openbeta_server
-
fixed FA18 Hornet Tacan INOP on MP Server OK in SP
JIGGAwest replied to Tomcat388th's topic in Multiplayer Bugs
is this both client side and server side setting, or otherwise? -
Monthly Bump. Still available.
-
untilhttps://discord.gg/Zh3BjBNC?event=1146770329549676575 The event is password protected. Please visit our discord and let us know your interested in attending the mission.
-
SOLD SOLD SOLD!!! VPC MongoosT-50CM3 Base SKU: VPC-109-001 USED - $260 shipped firm Base, tools, springs, cams. Clean, fully functional no issues.
-
VPC MongoosT-50CM2 Base SKU: VPC-109 Base, tools, soft/med/ hard springs, desktop mount kit, USB cable all included. Clean. Fully functional, no issues. USED - $180 shipped (US ONLY)
-
Graphics settings / tooltips - indication of FPS impact for individual settings (i.e. RED = high, YELLOW = Medium, Green = LOW or NONE) - Built in UI or in game setup checkbox for MFD Export settings. (Manual LUA programming is a nightmare for most) - Access to Special Options menu while loaded into mission/module (currently only available at main menu settings) -Moveable / scalable UI overlay elements (controls indicator, AI menus, etc) DCS World Web.exe (installer) / DCS_updater.exe -How to force install to a specific Drive other than C:/ -How to Launch a repair Module Specific -Access to module manual as an overlay like kneeboard - Swap between Mouse camera control and Mouse cursor control - Left Alt + C - selection wheel overlay Bindable ATC, Refueling, world interactivity commands (like jester menu) F-Keys are a pain, numbering isn't consistent
-
Works for me. 109.10 ILS frequency Runway 17 ? I believe. Are you approaching from the Las Vegas side ? Approach from the race track side. Follow the ILS chart for Nellis in the kneeboard for proper approach.
-
Instead of defining separately UIMainView and GU_MAIN_VIEWPORT You can instead use. UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center You also have a , after the last } in the center definition. This could be an issue. And you missing another bracket } to close out the viewport. The location of the last bracket currently is including the LEFT_ MFCD. Try deleting that. _ = function(p) return p; end; name = _('1 Screen and MFD Screen'); Description = 'Configuration with 1 main monitors and a small MFD' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } LEFT_MFCD = { x = 2552; y = 8; width = 480; height = 480; viewDx = 0; viewDy = 0; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center