Vakarian

By coincidence I've found that it's impossible to use cursor click to activate robbie tank on FUEL page. When cursor is over the text it doesn't highlight. Other buttons are clickable as demonstrated in the track. When clicking the L2 button on MFD frame (by mouse or using the bound action on my cougar MFD) it works without an issue. On FLT page, same issue with -w- action on L5. Clickable with mouse and button, but not with cursor. I haven't been able to find another action that's unclickable, but there might be more. unableToClickWithCursor.trk

Ah, sorry guys. For some reason I thought it was actually included in the latest hotfix, but I gave the changelog another look and found out I was mistaken. Don't know what happened Yeah, I understand the complexity and seems like I've seen it somewhere and took speculation for granted. Will watch out better for that next time.

Just want to ask question to make sure I understand how it's supposed to work before I assume it's a bug or something else. Yesterday I have flown with my buddy in the Apache and we wanted to switch seats. I was in pilot, he in CP/G seat. So what we tried to do was for him to leave the seat, I switch to CP/G and then he joins in the pilot seat and we have effective position switch. For this to happen I landed the bird to minimize the issue of desynced flight controls. The issue I had was when he vacated the CP/G seat, I couldn't switch to it. I have verified that the controls for occupying the seats are bound (default keyboard bindings) but it didn't help. Is switching seats getting disabled internally when someone other joins in? That would be the logical explanation why I couldn't switch.

IIRC it's if you WAS weapons on collective, only collective trigger will work. Same as if you WAS weapon on TEDAC grip, only that trigger will work. So you can't WAS weapon on collective and then use TEDAC grip trigger to fire whatever you selected.

I'll try to chime in to why people want trim reset from a gamer perspective. I know we are getting it, I just want to offer my clarification to people why is there a need for this. Now, as far as I understand it, IRL you press trim, move cyclic where you want it to be, release trim and it stays there. Now, when you want it trimmed somewhere else (anywhere else in the cyclic range of motion), you repeat the procedure. Here is a critical difference between IRL and DCS. In DCS this is not possible (full range of motion being the key here). To demonstrate, here is control box indicator with me sitting on the ground with everything in neutral position. Now, I'll trim cyclic somewhere in top left quadrant. You see the X where the trim was set. The issue is if for demonstration purposes I now want to trim my cyclic in the center of bottom-left quadrant. This is not possible. I have pulled my joystick down to the physical stop, cannot move it further, and you see that in game I can only retrim cyclic somewhere around the middle position in pitch. So If I want to trim my cyclic I would have to first retrim it somewhere in the middle and then retrim it again at my wanted position. There is no possibility to retrim in-game cyclic to any other place in the original range of motion, we can do it just in the square region around the trimmed position. (You can see in screenshots just how far down and right I can go with my physical controller) This is the disconnect between IRL and DCS and why I believe a lot of IRL pilots are wondering why we gamers need this. This is a limitation of how controls are interpreted in game. As we don't have controllers that stay in place like they do IRL, in games that's "faked" by moving the center position to wherever we pressed trim. Downside of this is that this basically removes the full range of motion. Trim reset, however fictional and unprecise it is, is a way for simmers to get back that full range of motion quickly, rather than trying to guess where the central position is, trim it there and from there trim what we wanted in the first place. Yes, there is a possibility of a wobble or a sudden pitch/roll motion if you don't predict correct cyclic position when you press trim reset, but I bet it's far better approach than what we have now. Yesterday I crashed because I was trimmed for fast forward flight (was wanting to see how fast can I go) and when I wanted to slow down, I got into trouble as my physical controller was pulled all the way down, but in reality I was barely centering the stick in DCS and it took me a bit to remember that I trimmed and I need to correct it it resulted in fumbling to get trim to central position, retrim from there and down in flames I went. If I had trim reset, I'd mash that button, get in a bit of a wobble, but I would have full range of motion in the cyclic and I could have gotten out of the situation.

This may be just my lack of knowledge, buuuuut in these modern days aren't controls set-up in a way if I do cyclic forward, they apply that change on the swashplate in a way that accounts for the gyro precession? If that weren't the thing, then if you wanted to fly forward, you would do cyclic left/right (depending what you fly) instead of cyclic forward which you do.

Eh, the bigger issue is that these aren't voiceovered. If that's not an issue, then you can add custom callsigns yourself which will be fine for SP, and in MP you will have to share that lua file with the participants, but it is doable. As a workaround ofc I too would like to see more callsigns for other airframes, but they should have matching voices. How it is currently seems like one step forward, one step back. We have new callsigns for F-16 and F/A-18, but I have to look at the text to see who is AWACS referencing

I'm not saying it's not easy, but if a dev first have to reproduce this by himself, that issue is probably going to the back of the queue and ones with either reproduce steps or a track showing the issue will get fixed sooner.

Well, if that track is huge, than try to reproduce it on a smaller one? You know, actually try to help with fixing the problem?

Unless you don't have a HOTAS that supports it (5-way HAT switch or TDC with push), you really shouldn't be using that TDC Action/No Action Toggle. Instead you should disable easy mode TDC in special options and use TDC Down (Action) control. It could save some of you a lot of trouble when things aren't going as expected as that easy mode is a bit weird at the times

You do understand that you have to extract files from the archive first, no? You download a .rar file, you extract its contents somewhere (.psd files) and then you will be able to manipulate them in Photoshop.

Got the 3D printed files laying on my table for 6+ months, so I figured it's time to try to get the electronics side fixed... I did look through the number of PJCR forum threads to regain as much knowledge as I can as I haven't done anything like this since high school... Could anyone take a look and see if the wiring diagram makes any sense? Main idea is to use 16 channel multiplexers to take care of the push buttons, and then wire everything else directly to teensy board

When you open it in the software that can manipulate .psd files (Photoshop, Gimp, ...) there is an option to turn off that layer and you just disable that layer. That will fix the Pave Penny issue

This was all covered 2 months ago, so I really don't see the point of necroing this.

MPRS has a boom, that is correct but it is inoperable in DCS. To use boom refuelling capabilities, you need to use KC-135, not KC-135 MPRS.

Hmmm, interesting that you noted it. I also have UH-60 mod... Will try to fly without it and see what happens

www.google.com I'm fairly confident you'll find all you need there

You are not the same. I've experienced it twice in the last week in A-10C II. From startup up until stepping onto runway all was fine. Then I do the run-up to prepare for takeoff and engine sound seems to just go away. If the gauges didn't work I'd have no way to know that my engine is running at all. The bad thing is that those were MP sessions and I had trouble replicating it so can't provide the track.

https://www.digitalcombatsimulator.com/en/downloads/texture_templates/a-10c_template/ There you go

You can use same template for the A-10CII as for A-10C. The Pave Penny is just not shown so it's not an issue (just disable that layer and you'll be fine)

Well, stuff like that can happen. That's why you have ILS to land in that kind of weather or you don't even take off unless you feel confident

Yeah, why not

No, they just assume that the playerbase is willing to put teeny-tiny bit of effort in to learn stuff. This is a simulation after all, you won't get everything on a silver platter. Use what you have between your ears

Eh, you stop seeing if after a while, get used to it

Dude, you made my day Will never be sick of that. But yeah, probably need some recalibration in the radio 2 channel output. As it's only showing on radio 2, most likely it's some sort of font bleed-off