wowbagger

My Vaicom always writes to both a DCS directory and a DCS.openbeta directory in the Saved Games directory. Is this normal behaviour? Is there anyway to stop it doing so? I only run the open beta branch so I don't need Vaicom creating a DCS directory every time it runs. The main problem is that Simshaker for Aviators looks for a DCS directory in the saved games directory and uses that by default. Only if there is no DCS directory does it then look for and use the DCS.openbeta directory. So I would like to have Vaicom stop pointlessly creating the DCS directory if possible. Thanks for any help with this.

Excellent. Thanks for the speedy fixes.

Wow, thanks for looking at this with such detail Flappie. Much appreciated. Unfortunately, I'm more than a bit out of my depth here and haven't any idea what the "PlaneSounder" class is or what it's related to. :(

I have had three CTDs after being hit by incoming missiles in the past couple of days. Each time the log file seems to indicate something's up with a sound file : F14_PILOT_COCKPIT:foley/damage_impact or F14_PILOT_COCKPIT:foley/damage_missileimpact. 2020-10-22 16:02:51.987 DEBUG Scripting: AWACSCallsign:make 2020-10-22 16:02:51.987 DEBUG Scripting: Phrases make : key = 2 2020-10-22 16:02:51.987 DEBUG Scripting: Phrases make : key = 4357 2020-10-22 16:02:55.068 DEBUG Scripting: Phrases make : key = 4258 2020-10-22 16:03:04.862 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_impact): gain 2020-10-22 16:03:04.864 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_missileimpact): gain 2020-10-22 16:03:08.091 INFO EDCORE: signal caught: 'Abnormal termination' 2020-10-22 16:03:08.093 INFO EDCORE: try to write dump information Any ideas on this one?

It's harder to read. It feels like twice as much clicking and scrolling to get the same information as before. Some utility is simply gone. Change is fine; but there is change for the good, and change for the worse. This was a horrible decision from the user's point of view, in my opinion, whatever the real reason for doing it is. The sole good thing about this change is that it will free up some of my time since I don't see myself spending much, if any, time here after this deeply disappointing new look.

+1 Do not like.

Nice work around, good idea. Thanks. Actually I do use something similar with my mouse. One of the buttons on my mouse toggles TrackIR on/off, another switches between mouse pointer and mouse view control. Then I use the mouse to look around in the same way you use the trim hat. Like you said it isn't ideal at all. But it works. I might try to come up with a macro that pauses track IR and switches mouse control with a single button press and reverts back to normal when you let go of the button. I think there are enough Track IR users to warrant ED looking at some kind of adjustable bias system as skypickle suggested - simply move the center point according to how far you look in that direction with a slider to adjust how much offset should occur. That would solve the problem. What are the percentages of TrackIR users vs VR users I wonder?

Awesome! Thank you.

Nice! Thanks

I have this in all my modules I think. I always have to hit 'normal zoom' at mission start to get the proper field of view.

No, it's simply how the two systems work together. The Scorpion will always be in the centre of the display, and the Track IR works by turning your head (ie, away from centre). So there will always be the weird sensation of turning your head one way and your eyes the other. My axes work well and are comfortable for every other aspect of flight simming. Trying to adjust to minimize this would make them far too sensitive for normal use, I suspect. The problem isn't as evident in the Hornet/Viper/Blackshark because I tend to be looking at smaller angles from centre with those, minimizing the problem.

Or what do I need the new one for? (It's rhetorical, by the way.) I'm not complaining about the II. Just not sure I needed the new toys.... yet. But it took me eight years to start enjoying the Hog at all. It'll likely change.

Yep, I'm struggling with the Scorpion + Track IR too. I never noticed the issue with Viper/Hornet, but with the Scorpion, at high angle of head yaw, I have to turn my head one way and and my eyes in the opposite direction to keep the Scorpion pointed at the right spot and actually look at it myself - rather unnatural and uncomfortable. I find things more comfortable with A-10C to be honest. But then I really don't even enjoy using the Tpod that much. Maybe I'm more of an A-10A kind of person. Feels like too many of the DCS birds are just Tpod bomb transports. I kind of prefer old school I guess.

I'm not sure if it has been mentioned already, but I noticed that some of the dials will just spin ad infinitum without ever hitting a stop. I saw this behaviour with the UK DÄMPNING (RWR audio volume) knob, PANEL BEL (Panel lights), and INSTR BEL (Instrument lights) knobs. Cheers

Has anyone replaced the battery in their UTC Mk II? I fear mine is on the way out since, after some years, it has started to not hold its charge as long as usual. If anyone has a link for a replacement battery that can be ordered I would be grateful. I love my UTC and I hate the idea of it dying and not being able to order a replacement anymore. Cheers

Yes, this affects me too. It seems random, or least I haven't figured out what is triggering it. Most of the time I get no waypoints shown for my flight plan (it does show those for the AI flight plans). However, occasionally it does work for my aircraft as well. Would love to get this sorted. :(

Is there a way to get Jester to toggle ALT NUM and VEL VECTOR options on the TID, apart from hopping back there and doing it yourself? I find the TID gets cluttered and crowded very quickly and it'd be great to have a hotkey to pop these off/on to get a better view of what's going on. If there isn't a way, please consider this a request. (If it has already been requested, apologies, and consider this added weight to that request.)

I haven't started the campaign yet, but I want to agree about the labels. Please let the player decided if they need to use labels or not. There are too many combinations of computer equipment, physical eyesight, and difficulty preference out there. No one but the actual player can decided whether using labels or not makes sense for their current situation.

I've just spent the last week (after 8 years of owning it) finally learning to fly this helicopter. This all sounds rather depressing.

Oh, I have no idea. Hope not.

Yep, I am indeed referring to the in-game ones. ED was smart to bring Bunyap onboard. Now they need to hire Baltic Dragon and have him producing campaigns for their modules full time.

I really, really like the training missions that Bunyap has put together for this bird. He has a wonderful tone and tempo and explains things at an appropriate level without tons of abbreviations. The missions are clear and succinct, allowing you to concentrate on the main point of the mission without a lot of tangential stuff. They build on each other very nicely without repeating the same stuff. I feel like I'm watching his older tutorial videos once more. I'd love it if all the modules had the benefit of Bunyap's expertise for their training missions. Anyway, well done Bunyap. Looking forward to more Viper goodness.

Thanks, I enjoyed watching these! They have rekindled my interest in mastering the C-101. Did you perchance post your missions for download anywhere? The biggest failing of the C-101 at the moment, in my opinion, is the paucity of content for it. Any missions are very much appreciated.

I guess the point is that even if the auto-hover is a real system, the real pilot likely isn't relying on it to employ weapons. He can retain full control of the bird, while the co-pilot does all the weapony co-pilot stuff. They can have full co-ordination with no need for the picky auto-hover system at all, but at the moment we cannot. For a single pilot, it just doesn't work smoothly enough as is. I'd much rather have bigger window for auto-hover to engage, an audio tone to tell me it has engaged (and disengaged), and some kind of semi-auto pop-up function. Then it would feel much more like the kind of smooth coordination a two-man ship enjoys. I'm all for realism in flight sims, but practicalities which cater to the fact that it's still just a video game should be equally important. I have pretty much shelved the gazelle until they get multi-crew working properly.

Glad to hear it. Thanks for the information My biggest problem with the Gazelle is that there haven't been enough concessions made to having a single person operate it. The auto-hover is a little too picky about initiating starting conditions. There should be a light or a tone to indicate auto-hover has engaged instead of having to keep the big red controls HUD open all the time, or wiggle your rudders trying to guess if it has. And the collective control from the co-pilot position is quite to difficult to operate smoothly. An automated pop-up feature, or simply a key binding to raise and lower the chopper by a metre at a time would make fighting in the Gazelle a lot easier in my opinion. As it currently is, I enjoy flying her, but not combat - I end up spending too much time faffing around with the controls and can't keep my mind on the actual task at hand.