Hoirtel

I've never liked the "mission start" trigger. Try changing this to once with the same condition, it should run after 5 sec if that is what you are after.

Haven't used ST in months! Goodbye old friend! Glad to see things are moving along.

If you are on a takeoff or landing, with the pedals on nosewheel steering then the slightest touch will send you off. Once you have speed up then the rudder is all you should use. How nosewheel steering is managed varies between modules, for those that have a nosewheel.

It takes a bit to get your head around at first but then it's fairly simple. Especially if you only have a small number of in/outs. I did once help somebody else with it. Post may help you too. https://forum.dcs.world/topic/290526-dedicated-haptic-feedback-for-bass-shakers-and-the-like/?do=findComment&comment=5367671

It's free to use. It is a mixing software that allows you to manage sounds in and out. It has good documentation + YT tutorials.

You can do this with voicemeeter if you are interested in running game sound through it. The applications add telemetry. Personally I use game sound with high frequency cut off through 2x transducers and love it. Uninstalled the telemetry, but most seem to like it.

Anyone know if meta has fixed this yet? Is it safe to update from v67??

I've bound the steering knob as an axis with a modifier to my pedals. I used the paddle on my joystick for the modifier. Whenever I hold the paddle I can steer with my feet. Not realistic I know, but then neither is using a keyboard or mouse....

I thought the AFCS should be off for taxi, not sure though. Agree it needs the lightest of thrust power/collective and then bit on and off the brakes to get it to roll. I also set a modifier button which I hold down and then my pedals do the swivel steering. Maybe not realistic enough for some but I don't have another axis I can use for the steering. Once its rolling it starts to get quicker but then it can ignore the steering so care and practice needed!

Glad you got it sorted. On a similar but unrelated note I have also experienced modules responding differently to peripherals. I had a button box that worked in Apache but not/partially in many other modules. Probably just have differences in the way they are coded. I fixed the box with a firmware update.

I think you might have had the same problem I did a while ago. On my MFGs I changed the angle of the pedals and did not do one side up tight enough. Couldn't feel a difference but that side had intermittent issues. I fixed it by resetting the position. Doing them up properly and the recalibrate all axis in the software. Never had an issue since. Currently my MFGs are flawless in all modules and work in the CH47 too.

Well I had real trouble flying this thing. As usual first thing I learnt is the cold start, which inevitably means I miss the odd thing. In this case it was the AFCS, pretty sure wags didn't do that in the quick start video. Interesting handling. Sometimes I can get it stable then when trying to push forward the rear rotor feels like it gets more ETL and pitches the aircraft down. Also any sideslip causes hard fishtailing. This seems very realistic although I have no idea really. Next time I'll try the AFCS....

DCS does seem to be worse with more units now, shame as the terrain rendering side of things has improved. I have always had a particular issue with Nellis AFB. Really unsure why but it seems completely unable to handle any statics. I did some perf testing between Nellis and Incirlik, both empty maps aside from statics at the airfield. Nellis just gets really bad, maybe it's such a big area and all units have to load with no culling. However Nevada in general isn't great, even with the oldest textures.

Well after the last meta update fiasco (v62-v63), I have taken the advice of someone in the thread from that and blocked oculus in and out of my firewall before it forced the update. No v68 for me.

Hi, I am hoping someone can help me with some up to date information on how to see the saved games liveries in model viewer. I have done this in the past but always struggle when I need to redo it. I can only find old information on the forum. I have a lua autoexec in the ModelViewer saved games. I have tried scan_for_textures("C:\Users\<PCNAME>\Saved Games\DCS.openbeta\Liveries") and mount_vfs_liveries_path("C:\Users\<PCNAME>\Saved Games\DCS.openbeta\Liveries") Couldn't get either to work, I also tried some combinations of backslashes, forward slashes and double slashes. One of these did give an error so it was doing something. I also may have tried removing the quotations. Any help greatly received - I am sure it is syntax related but can't find out.

Hoirtel

Awesome, thanks for your work. These look great. Also big thumbs up for sticking to the core units.

Hi @Hammer1-1 I don't have a group or squad but also have similar interests and looking for similar type of flying partners. What times do you usually fly?

Oh... Interesting.... Well I have used it quite a lot although only in 2 person co-op (on dedicated server). As with any Comms we always test as early on as we can and those colours I always see. I have never seen green when I have transmitted, only red. I saw the green when my wingman responded. I must admit it always seemed counter intuitive... red is good, green is also good. Yellow is neutral. Only one that made sense is gray = off. Some of the people I flew with have had issues, and in this case I would see the green transmit and hear the click, but not get any voice. It seemed that there was always a config issue somewhere on Thier end as redoing bindings and/or headset plugging seemed to fix. It did also sound like one person had some conflict with background applications but as I am not there looking at the setup I can't tell for sure. It's a shame there isn't an easier way of troubleshooting..

There are no additional ports to config for voicechat, server admins just switch it on - that's it.

Very interested in these, love my virpil warbird but FFB would be worth the money. For me to purchase I will need to wait until they are out, well reviewed and hopefully some teardowns. I expect there is a lot of opportunity for the internals to fail if this is not done properly. They need to get the price and quality right.

In the past I have found vsync setting to fast very good but in last year or so set this to application controlled and set my DCS FPS to 85 for an 80hrz headset setting. I find this helps with some artifacts. Do any Q3 owners use the openxr toolkit now it's not longer in dev? I basically only use this for a bit of foveated rendering and minor super sample, which I can probably do with PD. Haven't tried DLSS/DLAA since release as I really didn't like the smearing. I use a 0.2 super sample with 2xMSAA.

Red is transmitting, green is receiving, yellow is on with no traffic, grey is off. If you are all in coalition but greyed out, I think that means you are all in radio mode. You can move between the Libby rooms by clicking on the name. If in spectators only common is available. Once you in slot you move to coalition, but also radios become priority. People I have used it with seem to have trouble at the start. Very often seems to be config as after several rounds of redoing all the same bindings and settings it seems to work. Can't say if they had it right first or not. My voip seems to work all the time but I don't unplug/replug my headset or peripherals and keep PC clean and trim. Who knows.

So I think I cut too much, nothing seems to work properly. I have restored to a fresh profile, but cannot disable commands in batch. Is there any quick advice you have for making the F4 commands only the crew chief and jester? Sorry - hate to ask you to help undo all your hard work but these aspects are so good and the others conflict with my own profile.

My experience with VoIP issues recently have all been down to client config. Somehow people just don't seem to understand it, and can't get their head around the three or four buttons they need to bind. I have had people say they prefer SRS "because it's simpler" when I point out the whole separate application with separate bindings, and pages of settings and options. I think VoIP needs a wizard to help those that for whatever reason, just can't figure it out. I say the above because it comes out sooner or later that "oh I didn't bind X" and then suprise suprise it we can speak!