Snacko

Just tried to bind a keyboard key to the "Probe Control Switch - EXTEND/RETRACT" toggle, but apparently a keybind is not allowed for this command??? It won't open the key bind window. Same for the "Probe Control Switch - EMERG EXTD/RETRACT" command. Possibly this has something to do with the 'Special for Joystick' category? What is that?? I don't see anything about it in the Early Access Guide..:joystick:

Have you selected it using the Systray icon? Sent from my Moto Z Play using Tapatalk

I have been trying to make my text larger in the Training, but no joy!! Does anybody know how to do this?? I thought it would just be the basic mission messages, but my mod seems not to adjust text size anymore.. I have tried several things over the past 3 hours, but am getting nowhere.. EDIT: Never Mind. I started over this morning with a clear and sober mind. And I think I have it working.. This is with a Font of 20. Might make it a bit smaller, but it helps a lot on bigger screens.

Thanks, I just didn't want to waste my time struggling with something that was not functionally implemented yet. :wallbash: Snack

As the title says.. F/A-18: Is there a list of currently working features and systems? Thanks!

Who are these 363 Guests? That's a lot of lurkers..

Actually, this does hurt me since I bought the table top version so I would have the base in case I ever wanted it. But I am waiting on the center stick extension, because my original intent was to mount this centered. So, I have my VKB MCG sitting to the side waiting for the extension. My mistake was assuming it would be no problem to wait a month for the extension. I just hope I don't have to wait 6 months like some of you have said.. Argg..

PS: I just flew it again just now, and there were runway lights. So it must be just flakey and buggy? And I didn't even contact ATC.

This was at 4-5am I believe. Taxiway lights are there, but no runway lights. And there were not even any taxiway lights until after I contacted ATC.

No runway lights at Mozdok. Contacted Tower and got the taxi way lights, but no runway lights.

As posted above, I have had this Crash on Exit from the game for almost a year in the Stock, Beta, and Alpha versions. With this last update it seems to have been fixed. I've waited a few days for testing because I didn't believe it. But it does seem to be fixed. Not sure if the game was fixed, or an update on some software(AV/FW) or the big (April) Windows Update that was installed the day before the DCS update or what.. But it's not crashing on exit finally..

Then, why don't you accept pre-orders? Take an order, and credit card info. And don't charge anything until it's shipped? You will then have a better idea of how many to manufacture, instead of being 'sold out' in Europe and not available in the USA. At least all those customers who have been waiting for months would know their products are in the next batch, instead of having to watch, day after day to 'jump' on it as soon as it is finally available. Which is super annoying if you have been waching and watching and then find out it's arrived, but sold out because you weren't able to check for a few days. :doh:

IDK.. it seems like they think it's fixed or not a problem anymore.. Sent from my Moto Z Play using Tapatalk

I just wanted to document this solution because Helios has a habit of "randomly" starting to crash. I've had this a few times over the last years and it was always very difficult to get working again. :joystick: :joystick: Helios was working flawlessly until yesterday. The bam! It started to crash on startup. Both the Control Center, and the Editor crashed before they even loaded. The event viewer said it was an xml parse error. I uninstalled Helios and reinstalled only to get the same error. It uses the 2.0 Runtime so I tried reinstalling that, but could not. Win said it was already installed. Ran a repair on 2.0 and it found nothing to repair. Reinstalled DirectX, but no joy. Finally, I figured out (after a bit of prayer) that the ..\My Documents\Helios\HeliosSettings.xml file was full of null.null.null.null.null.null.null.null.null.null.null.null. Delete the file and let Helios create a new one. And that FIXED it!! Helios works fine again. I think what happened was that after a Windows BSOD that I got upon shutting down Windows, that file was not written correctly and filled with nulls. That's why I started getting Helios Crashing on Startup with some XML Error. This file is not in the Helios 'install' folder. So, uninstalling and reinstalling Helios will not fix this problem! And this file is in the folder with all of your Helios profiles. So, you don't really want to wipe them out too and loose all that setup work! So, that's why it was so hard to fix..

I'll test it out again when I get home. It should still work. It's usually just 1 thing people forgot.. PM me and I will try to help if you want .

What aircraft were you trying to export?

Neil, I am interested in this profile. I don't have many problems using the Helios Editor for the simple tweaks that I have done. Also the video would be nice. And even just a screenshot of what you have now.

@f4l0 Roger, thanks. It works perfectly.

My pc just installed a new SS for Aviators update and popped up a message saying the Sound Module was a separate install now? I don't have a Jet Seat. I only have my own amps and shakers. So, do I need to uninstall SSA now? And only install the Sound Module? Sorry, I'm a bit confused..

I was getting a ton of traffic driving right through vehicle columns that I put on the roads. So, I turned the Civilian Traffic down to low. But I still see tons of cars and trucks on the roads. Can someone check on this? It doesn't seem right... Too many vehicles all over the place for Low..

I'm flying the Su-25t and noticed this.. Why is the RIGHT_MFCD viewport semi-transparent? The Shkval in the cockpit is not semi-transparent. This needs a background to be functional. Can this be fixed? :cry:

Mine just updated the updater. Probably getting ready so it can do the F18 update in the near future?

Are you playing the stock game or the beta? My stock game works ok with Reshade 3.1.1. The beta is having the problem.

I see in the log a reference to DirectX 11. Does DCS use Dx11? Is this something new? I had Reshade 3.1.1 for Dx10+ working fine for months. I think the + indicates that it should work with later versions of DirectX, like 11? Then I noticed a few weeks ago it started crashing the game on startup, so I removed it. I have just updated to the latest version, Reshade 3.2.2, but that did not help. Here is the crash log. It's strange that the lines say INFO, and not ERROR.

Just wanted to post the solution to get English Radio calls for Russian Aircraft. Overwriting the Russian speech sound files only partly works... The only real working solution is to add those aircraft to the USA (or other English countries) in the script database so they use the country's native language. https://forums.eagle.ru/showpost.php?p=1895645&postcount=5 I just did this for the Su-25t and it works great. It probably won't work for MP though..