sze5003

Ah thanks for that. I could have sworn I tried 4518 but just saw a flat area with buildings. I'll try again. I was scrambling since I play in VR and by the time I didn't see anything from the coordinates I punched in from wingman, i decided to try the coordinates that I heard back from overlord on the confirmation call which were different probably due to a typo or something.

Hey! Loving the campaign so far! When we reach waypoint 7 or 8 we are told there is fire and smoke at our 2 o clock but I'm not seeing anything around those mountains. I have chimney smoke set to 3 in settings. Civ traffic off. The coordinates from the F10 menu say KN 9444512 but overlord reads back 944 452. I checked both but was not able to see any troops or BTR's in the area. I'm seeing a flat area with several small buildings and what looks like a river in the area. The buildings looks like small garages and warehouses. Not sure which coordinates should be the right ones.

I was a bit confused about the navigation as well. Many times the pilot seems to go straight and then veer right or left a few times. I thought he was trying to align the NDB line on the instrument panel but that didn't seem to be the case. Maybe a small description of what we should be paying attention to on that instrument would be helpful. I know the line points toward the station frequency, but are you suppose to follow it or fly a course to it so that you intersect it at some point? Since this plane doesn't seem to have a lot of need for many hotas commands maybe mapping some of those to the kneeboard to see the waypoints will be helpful, specifically in VR.

Check your controls, it must be bound to something else. Either in an external program that interacts with dcs or within DC's itself.

Which pedals the tfrp or the new $500 ones?

I also have a mcg pro grip and what I do is use the warthog slew mouse and I've assigned the tdc depress to the down press function of the 5 way thumb button on the mcg pro. I imagine this works as long as you hold that button down and slew. I don't use any of the other hats on the grip to slew since the stick is very sensitive to movements and it throws me off my flight path if I do.

It's not. I just remembered watching one of the preview videos on YouTube, either spudknockers or magz and one of them mentioned due out by the end of January.

If I see a Baltic dragon logo in a module or campaign I'm buying it day one lol. Very nice work on these training missions. I like the Russian accent too of the instructor. I'll be getting this module next week while we still wait for a firmer release to the tomcat.

I also think you need steam VR beta installed too. When I tried this expirament, wmr is under the software section at the top where you can filter by games/apps. I set wmr to open beta and it just said beta next to the name but when it booted up it looked the same as before until I updated steam VR to beta too. Either way I am back on the stable steam VR and stable wmr app. You can still scale resolution to 200 without the beta. Open steam VR, go to settings, on the left side select video and then tick the checkbox that says manual override. Mine already said 200 when I ticked that box.

So I right clicked windows wmr for steam VR and went to properties, selected public beta and restarted steam. I'm not sure if it's in beta actually. It says it next to the wmr app name in steam but nothing changed and in settings the rendering is still at 100% Edit: Seems you also don't need steam VR beta or wmr for steam VR beta. In regular steam VR under the VR settings, video section, you can check manual override and you will see resolution is already at 200%. You can keep this manual override or you can turn it off and only set 200 for dcs under the application tab when dcs is running. Either way I get about 40-60 fps over cities with msaa off and PD of 1.5. PD of 1.0 and 200% resolution in steam to me looks like 100% resolution and PD of 1.5 without the target rending set to 2. So to me it looks the same not sure what the expected difference is supposed to be.

I swapped out for the #30 cams and re ran calibration. Included the trigger this time. It feels a lot better. Going to have a flight soon after DC's updates. Very happy with the centering now. Thanks a lot for the help. I'm sure I'll be back with more questions later. The process to swap the cams was very simple and I was afraid I would screw it up. I made sure to put the washers back in the right order too. For anyone wondering you need a 7mm wrench or socket wrench for tightening and loosening the cam bolts. It was way easier than I thought. Hold the Allen key in place on the one side and loosen with the wrench on the other side of the cam bolts. And also springs didn't go flying off into the abyss of my room so that's a plus for my first time doing this.

Yes I'm assuming also no pixel density is standard 1.0 in the DC's VR menu option. I'm not running beta yet so mine is still at 1.5.

Ok so then it seems normal. I'm going to change the cams the the 30's. Keep the original springs on it and possibly also keep the clutches the same way I have them now. I just hope to have the right wrench for the bolts. I didn't see anything in the box except the small Allen key it came with but I'm sure my toolbox will have something.

Thanks for the reply. Here are the screenshots I took with VKB JoyTester. The Response curve section under Profile tab of VKBDevConfig 0_87_05 was not reading movement which is why I used the Joytester program.

Perhaps I need to recalibrate it. Some of the values are within limits others are a bit high. Also might be a bad time to ask but I bought this from another member and it was brand new which he also gave me the invoice. I'm not expecting any issues but I just read the warranty is not transferable [emoji849]

Thanks a lot for the answers everyone. I ended up loosening the dampers a lot until I can see the top end of the screws. Stick now returns to center and flying is a little better. Still very loose and the slightest movement will cause tiny movements in pitch and roll but a bit more manageable. I will swap the cams to the #30 cams tomorrow. Probably keep the default #20 springs on and see how that goes.

Thanks but it seems that this render target scale has been auto updated to 2.0 according to the previous comments. I'll try and get into the beta version soon.

So I was doing the updated missions now. Do we still need to orbit waypoint 3 after calling in blackjack? Or do we go straight to waypoint 4 ?

Thanks. I'll give that a shot today. I guess you can run different cams on each axis? I'll first start by loosening the dampers more. Then I'll try your suggestion and swap the pitch cam to #30 if I don't feel like that does enough for me. I'll most likely keep the default springs on there. I'm glad vkb included a lot of options for springs. I don't use the extensions just the desktop plate and I made the mistake of using the heavy springs on the virpil base earlier which is meant for the warthog grip but I had not even placed the WH grip on that base so the center is too stiff now for desktop use I think. I definitely prefer the feel of the mcg with it's default springs because it feels a lot smoother.

So you mean loosen them all the way? I was under the impression that tightening the dampers more would make it go more to center. I'll try that tomorrow as I couldn't tell how much I loosened them. They we're not very tight out the box.

Set up my gunfighter mcg pro tabletop model tonight. I really like the quality of the break lever and two stage trigger handle. The base is beautiful and I loosened the dampers I think a little too much. It's smooth as butter and it's more comfortable to hold at least for me compared to the MT-50. Very happy with the quality. The software was ok to use a ton of options in vkb Dev config but I did a quick search on how to turn the second pov to a hat instead of an axis and got it up and running. I did have some questions that maybe owners here can help me out with. Now I don't fly the Huey much but I notice when I was flying the F18 and I would push down on the stick and let go it wouldn't full return to center. Made flying a bit wobbly in the jet. If I pull the stick back, it seems to return more to center than pushing it forward does. When forward it kind of returns but stays forward just a bit. I left the default cams and springs on there. I think I like the springs that came installed. They offer very easy and smooth push/pull on the stick. To get the stick to return to center more would I need to tighten the dampers more? I notice it came with springs # 10-40 and a set of 30 cams. Would the recommendation be to keep the default springs and just switch out default cams for the #30 cams? I don't want to have to pull or push a lot from center but I'd want the stick to return to center from each axis maneuver. Flying and using the hats and switches is kind of tough now since it feels a bit looser while flying compared to just testing it out in the software where it felt right to me. In the F18 it requires can constant movement of the stick for it to not drift even when I think the stick is centered since I'm in VR. So would the #30 cams help me out or should I swap to a set of heavier springs? Really glad I finally got this model as I've been wanting one for so long. Just curious on how I can perfect it for my flying.

Awesome can't wait!

How can you tell if you are using wmr for steam app in beta? Or do you have to uninstall steam VR and reinstall the beta?

Good to hear thanks a lot for the update! Appreciate the time and effort to detail.

I have not done that mission yet but I would think they are using the laser guided bombs so you just have to have the correct laser code and ask for lase. Unless they updated the hornet to put in grid style coordinates, you would have to convert them.