Genchou

Hi Mith ! I really enjoy your training grounds, thanks a lot for your work on this ! One thing I noticed though is that a drogue tanker seems to be missing on the Gulf map (last checked with version 1.9). Maybe I'm missing something, but at the moment I only see a boom tanker (KC135). Is there a way to make one spawn ? Via the radio menu maybe ?

Had it occur a bunch of times, usually after a landing on the boat. Mostly the left wing, but it happened a couple of times with the right wing too.

I think the mod won't increase the actual slew speed, but the added precision and ease of handling will surely allow you to have quicker and snappier inputs when slewing. And you can always adjust your curves to your desired settings.

For now yes, but if you dispatch come June (as said on your website), the UK won't be part of the EU anymore and import fees and VAT will be applicable. :p But it's alright I'd say still worth it even with the taxes (it will a bit less than 70€ I think). I ordered this afternoon !

Hi Delta ! Your mod looks very nice, I'm thinking of ordering one. I just wanted to make sure about import fees and VAT : you ship from the UK ?

I think that's a fair assumption. Who would use SimpleRadio without a mic on a regular basis ? :p In my case, it's really more of a one-time scenario because I didn't have my mic with me at that moment. Thanks for your answers though !

I tried again by plugging in an old mic I found in a drawer and it worked without any issue. So it does seems like not having a mic plugged in could cause some issues. I know it sounds stupid to use SimpleRadio without a mic, but at that moment I just wanted to hop into the BlueFlag server and still be able to hear the comms, without having to buy a mic first. Hopefully I was able to find an old (broken) one. Edit : there isn't any issue related to sound input/output with my win10 installation so far. SimpleRadio seems to be the only software having problems. Edit² : @Gliptal no, I was not using Voicemeter. No voice/sounds software except SimpleRadio. Edit³ : I was taking a look at the source. The exception I was encountering seems to be thrown in MainWindow.xaml.cs at line 745. The try/catch seems to fail because at the line 734, you call the method AudioManager::StartEncoding with Mic.SelectedIndex set to null (or whatever an undefined var could be in C#). I could be completely wrong, but it seems to me that the no-mic plugged case is not checked. Maybe stop the procedure and trigger a warning message when the audio input select is empty, prompting the user to plug a mic in order to be able to connect ? Anyway I thing it should fail or exit gracefully when no mic is present. The biggest issue here is that the software was crashing (windows had to force-close it) when I clicked "ok" on the error dialog.

Hi, I'm trying to use SimpleRadio but it invariably crashes on me when trying to connect, with the error "Problem initializing audio output." Here's a screenshot of the error : When I click "Ok", SimpleRadio crashes and has to be restarted. I tried with every output option, all four of them being named "VIA HD Audio (win10)" but it always crashes. Is there a misconfiguration on my part ? Could it be linked to the fact that I don't have a microphone ? clientlog.txt

Edit : my bad, it was an user error. Somehow the G940 FFB was misconfigured. For anyone who would happen to have the same issue : make sure that the "spring force" (not "centering spring") is set to a high enough value. If not, DCS FFB implementation will behave as I described in my post. The FFB effect when trimming in helicopters seems to have been modified since the 2.5 update. Previously, in all choppers (except the Gazelle which doesn't support FFB), keeping the trim button down with a FFB capable stick (G940 in my case) would lower/disable the "centering force", allowing the stick to move without resistance except some dampening/friction. The centering force would come back to recenter the stick where the trim was released. This allowed a very smooth and enjoyable experience with choppers and FFB. Since I updated to 2.5, this behaviour is gone. Now, pressing the trim button won't release the centering force, making any cyclic adjustement jittery and unprecise because you have to overcome the center resistance. I should note that nothing on my part changed : no new drivers for my HOTAS, no profile change, nothing. Just DCS. Was this addressed in any way by ED already ? If not, I'd love for the previous behaviour to be restored. PS : I know about simffb but I'd prefer to have this built in DCS for the start, especially when considering it was previously functional.

I don't have sources in hand right now, but there was something about the warthog throttle being potentially damaged by inconsistent power sent from an USB hub and the possibility of having a peripheral not being recognized when not plugged directly on the board. Take it with a grain of salt though, I did not verify this, it was just some random posts I read some weeks ago on a forum. But I prefer being safe and ask here if it's okay to use a hub with the Warthog.

I don't have a free PCIe port, sadly. Yes that's what I was talking about, a hub for the sims peripherals in order to free up the board USB ports. So it's "safe" to plug the warthog into a hub for example ? I've read in some places that the throttle in particular could present some issues when plugged into a hub.

Hi guys ! Quick question regarding the Rift : I'm currently considering buying one and I've been concerned about the lack of free USB ports on my computer. With mouse, keyboard, the warthog and a rudder, I'm only left with one free port. How do you manage this ? Is a USB hub viable for sims peripherals ?

Are the team registrations automatically distributed ? I followed the link to register (http://www.buddyspike.net/blueflagreg) and received this message without chosing anything :

Edit: nvm

Wonderful news ! Your module is well on its way to be one of my favorite. Only thing lacking at the moment is the FFB, imo. I hope it will be added soon ! Anyway, thank you for this great helicopter !

I think what he was saying is that the issue here is maybe not a bug per se but rather the consequence of not using the correct ranging method in the code. That would mean that the ranging here is "working as intended" for the particular method (camera ranging tied to the ground), even though it is not the result we should have (by using a laser ranging). But I don't have the code so I may be saying complete BS.

I hope you can implement FFB soon ! Right now the module is hardly enjoyable if you own a FFB joystick, but I'm sure it will be a favourite when that is sorted.

Is the dcs_local_source.txt still relevant ? I can't find it anywhere on my computer, I guess it's not used anymore ?

If the post from Wags was deleted, there is nothing supporting that claim. We all noticed that -70% sales haven't been around for a while, but it's still possible that it could happen for Christmas for example.

Does anyone have a source on that info ? I don't doubt the fact but it's hard to explain it to my friends when I can't give them a quote from Wags or something similar.

I have the same problem and running the update again from the start menu doesn't help at all. The update fails everytime.

I could use that.

It's a matter of personal preference. Tearing does not bother me in most case and I have noticed that vsync can lead to loss of framerate in a bunch of games, so I tend to keep vsync off. I only turn it on if the tearing is reaaaally bad, which is rare.

Apparently it is only that one flap on the right side that doesn't open. But I'm no expert on the matter so you shouldn't take my word as a fact.

I may be wrong but I think I remember seeing that on real Fw 190, so apparently it is modeled after the real thing. Edit: Googled the thing and there is indeed a bunch of pictures showing the Dora with one flap closed: I'm not sure why the radiators open like that, but a quick Google-fu yields a lot of pictures so I think it's not a bug. :p