mx22
-
Posts
275 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by mx22
-
-
On 6/28/2022 at 8:08 AM, niklos4 said:
Hi...
As of yesterday my antivirus (kaspersky) flags the "DCS Updater Utility.exe" as contaminated by VHO:Trojan-Spy.MSIL.Convagent.gen.
Any input?
Thanks in advance.
Had the same happen to me last weekend. I've marked application as trusted in Kaspersky to allow it to run. But yes, would be nice if developer looks into this.
-
I think the biggest issue is that mouse device needs to be close to the surface to work properly. At that point, regular mouse is probably just as good...
-
Thanks, I figured it out - online price was already discounted, so it was only extra 10% during the checkout. Just waiting for them to process and ship it now...
-
Hello,
Not sure if I'm missing something, but what does one need to do to apply VIRPIL's 10% Christmas Discount to their order. I'm trying to order their collective base and grip - site automatically applies 10% Collective discount, but does not apply Christmas discount. Is there a code I should be using?
Thank You!
-
Not sure if it would help, but I had a problem on F16 getting the throttle to move from idle into off position (the one where you have to 'twist' quadrant to the back). What solved the problem was going into Axis Command screen and adjusting deadzone to remove the very start of the throttle movement (used by virtual buttons created in Virpil software). In my case, it was moving deadzone from 0 to 4 (I'm using 'classic detent' on CM3, so your value could be different). Also, make sure you are using the same axis for throttle input as for virtual buttons.
Interestingly enough, on F18, I did not have to do deadzone trick. Go figure...
P.S. Binding axis in DCS. I found you have to move axis all the way through it's movement before DCS registers axis movement. Not sure why, it seems a bit counterintuitive. You can also manually assign axis through dropdown menu.
-
I've just tried AirLink at 90Mhz and Virtual Desktop at 120Mhz in a quick Free Flight mission in F16. I don't see myself going back to wired Link, though I would really like to test how long battery lasts in a longer missions with either of these options.
Strangely enough, I had no keyboard problems in AirLink, but ran into some issue in Virtual Desktop - keyboard presses did not register at all at first, but started working a few minutes into the flight. Go figure...
-
Ahh yes, sorry I was looking at the menus - I thought it would work like the VR mod previously and would render mask everywhere...
-
How did you enable the mask? At least by default, I don't have one enabled and get the whole right/left eye render.
-
I've owned Rift S since it came out and just this weekend bought Quest 2 to see how it stands up to Rift S and if it's worth upgrading.
Picture quality and screen door effect - Quest 2 wins hands down. I'm on a somewhat older machine this day (16GB RAM and 1080ti) and performance between two is compatible when I set Quest 2 to 90Mhz. This is through third party 'Link' cable, I have not tried Virtual Desktop yet. I have ASW locked at 30Mhz and the only time I see fps drop is when I'm on a large airfield with a lot of ground units or flying over large cities at very low level - but I had the same problem with Rift S so it's a moot point...
As far as DCS goes, I simply fail to see any reason to go with Rift S over Quest 2. In my racing sims, I still need a bit of tweaking for a final decision - the most obvious problem for me is that all objects in the distance are somewhat fuzzy (for example road in front of me is sharp, but a tower over the same road in a bit of a distance is noticeably fuzzy/blurry) and I can't figure out how to fix that. It's a bit annoying given that picture otherwise is better that what I get with Rift S.
As it stands at this moment, I will probably go ahead and sell my Rift S in the next week or so. I've been really impressed so far with Quest 2 and personally think it's a much bigger jump for me then what I had when I went from CV1 to Rift S... G2 is probably better, but it's twice the price and my system probably won't be able to handle it as good as Quest 2...
P.S. Probably worth noting here, with Rift S the whole screen is evenly sharp, but with Quest 2 I found that center is sharp, but things get blurry towards the edges. Perhaps a smaller sweet spot. I really need to experiment more and probably get alternative face shields to see if I can fix it. It was really bothering me the first time I put the headset on, but I got used to this in about an hour/two and no longer notice it all that much.
-
1
-
-
29 minutes ago, Icebeat said:
I was thinking in buy one but after this, I will wait for a fix.
this could be a very long wait... just saying...
-
Just a quick heads up if anyone gets into the same problem... Virpil Support rescued the day for me - in Configurator tool settings (CTRL + F12) I had to enable 'Show Developer information (SetPCB)' option. This enabled manual selection of the base's PCB via a dropdown near the bottom edge of the app window. Once proper PCB was selected, everything started working.
-
1
-
1
-
-
So there seems to be a lot of 'first look' videos on YouTube, but I don't think I've seen any comprehensive reviews on either Libra or the new Orion. Are they worth the price? How's the feel of the movement, adjustability? How do these stack up against Virpil's Mongoost/Warbird?
-
18 minutes ago, rapid said:
And i take it you only have one Virpil device connected while trying to flash?
Yes, I only have Virpil's T50 base and grip. I've actually tried flashing on my other computer too where this would be the only joystick to be connected at all...
-
30 minutes ago, rapid said:
#This firmware has been patched as of today. Not sure if you are using the earlier version. Worth a try.
Thanks a lot for the heads up - sure was worth a try. Sadly, same result as before.
-
Thanks a lot, I actually stumbled across this page yesterday. Unfortunately resetting my firmware by shortening the pins did not resolve my problem. It looks like joystick flashes and updates firmware just fine via either VPC software or by first removing existing firmware via shortening pins as described in the link - I can see name update based on the firmware version in VPC software.
-
Just wondering if anyone came across similar issue. I've decided to check VPC software out and sure enough, I needed to flash joystick's firmware - firmware failed on the last step (after flashing the software and auto-rebooting joystcik) with an 'ERROR. Device PCB' message. Sadly, now joystick is no longer listed in Windows 'USB game controller' so I cant use it. VPC Configuration Tool however still sees it, however when trying to re-flash firmware I still get the same error with the same results. I've tried clicking on 'restore factory defaults' in the firmware updater, but it throws the error as well...
-
1 hour ago, VampireNZ said:
Just FYI - you are aware we can have different kneeboard setups for each aircraft right?
In any case, in my Viper kneeboard I also have the standard info such as freqs etc for each map, HARM codes with full DB list of all emitters if you want to swap one out of the tables, full Viper checklist from pre-flight to shutdown, also a Morse code cheat sheet for identifiers (more than one occasion in DLC Campaigns have been given duff freqs/I.D's/codes for navaids) and a couple of pop-up attack ref sheets for a few different profiles from a great online calculator someone posted a while ago.
Also have a separate kneeboard in my Thunderbirds mission with each manoeuvre on a page with specifics, then whole combined display on a couple of pages.
Would you mind sharing your kneeboard?
-
Yes, I've deleted the whole DCS.openbeta\Config\Input\FW-190A8 folder before reinstalling the module. I did not try changing controls after the reinstall, so I don't even have this folder anymore...
-
Controls are messed up
For some reason all of my controls are messed up - there are a lot of duplicate entries:
Also, my stick section appears to be all mixed up and looks different than what other users have (there is a thread in the main forums with screenshot):
I've tried running DCS repair, as well as deactivating module and installing it from scratch, but still having this problem.
Is there a specific file that I should perhaps try deleting?
Thank You!
-
I don't have 'a' or 'b1' options under stick category:
Am I missing something?
-
Yes. That's why you need the other ones to bind if you want to fire your weapons.
Can you tell me the names of your assignments and what they do? I already tried all possible options under 'Stick' menu (except of 'MG131 fire' which cannot be used on my end at all) and can't get wing cannon to fire. MG131/151 controls cowl gun only.
Thanks!
-
Neither 'Input.FW190A8.trigger_b2' or 'Input.FW190A8.trigger_t' do anything on my end when I assign joystick buttons or even try keyboard shortcuts. Also 'MG131 fire' cannot be assigned to anything. Anyone else with this problem?
-
I still don't get it.
Input.FW190A8.safety - works as gun safety (appears to be bugged as you can fire cowl guns no matter which position it is)
Input.FW190A8.trigger_b2 - does not do anything
Input.FW190A8.trigger_t - does not do anything
MG131 - does not do anything (and appears grayed out for keyboard and joystick bindings)
MG131/151 - operates cowl guns
Weapon release - did not test
Am I missing something?
-
I ended up fixing my problem by reinstalling DCS from scratch. Not sure if it will be of much help to others... My original installation was very old - 1.5, if not older and was moved from one SDD to another over the years, so I suspected something was conflicting in the game. On the plus side, DCS appears to run faster now too (though perhaps I now have lower settings than I used to).
New Virpil T-50 Base - Inbound
in VIRPIL Controls
Posted
Why would this be a competitor to RealSimulator? This appears to be an evolution of current T50 base with dampers or something similar. Not sure why they've used F16 for demo given stick was center mounted and on 120mm extension (F18 would have been more appropriate) so perhaps there is something behind this, but I doubt it is force sensing...