Adder76

Hi, MGM. Have you checked if Historical filter is activated?

I decided to play Normandy air to air mission for C-101CC after not playing that specific mission for a long time and I realized that Matra Magic missiles are not visible nor usable. So, I decided to try a mission made from scratch and these missiles don't look to be available at all, although you can select them in the mission editor. Sadly, I don't know if it's something related only to last open beta patch, the version I am currently playing, or it started happening some time ago... Anyone else is having the same problem?

I just took a look at the first movie and, unless I watched it wrong, the VF-1 emblem on the right tail is indeed inverted. I mean, looking backwards, as in the new skin. You can barely see it in the flat spin scene.

Thank you for your answer. Both pictures were taken with 1.8 gamma. I used to had that setting back in 2017, so I made the latest screenshot the same way, although nowadays I play with 2.2 gamma, the most common setting, according to what I read through this forum. I tried lowering gamma even to 1, but the shooting lights kept showing as not glowing textures... No one else looks to be affected, so I guess it's something that happens only on my own machine I'll have to get used to.

I took the F-15C for a ride a couple of days ago and I realised that the shoot ready lights are not very visible. In fact, they don't look as lights at all. Is someone else experiencing this issue? I'm sharing two images, one from when the lights changed from red to yellow and one I took a couple of minutes ago.

Sorry, but does it mean that having an 8gb graphics card will be mandatory in short term? That kind of graphics cards are absolutely skyrocketing right now. I'm afraid that buying a new one with that amount of memory will be prohibitive for many users. At least, for a long time.

Yes, I was talking about the home button, although maybe I should have been more clear in my explanation. If your'e pushing it and it's not working, I don't know what might be the cause... Maybe it's configured in PS3 mode? There's a small button that changes between PS3 and PC mode... Or it might be that the light is not working at all... When the button is red, the throttle paddles and the twisting movement of the stick activate the same axis. When it's green, each of them triggers one different axis. You can check what axis are working in Devices and Printers section in Windows. You just have to right click on the stick, select Game controller settings and click on Properties. Once you have checked you have all axis activated, you only have to assign them via DCS World.

I have exactly the same stick. If you press the red button, it will turn green and you will separate the stick's twisting movement and the rudder button in two different axis.

Sorry, I should read more carefully. This is each module size. Again, in latest Open Beta. Nevada: 33,9 GB Persian Gulf: 32,9 GB Tomcat: 3,15 GB Viper: 983 MB Hornet: 782 MB

I am in the latest Open Beta. Stable branch might be a little different, but, according to my calculations, latest installation with all CoreMods, SU-25T, TF-51D and Caucasus (which are also CoreMods, but are installed in mods folder within game's installation), Viper, Hornet, Tomcat, Nevada and Persian Gulf might take 145,38 GB. I hope you'll find this information helpfull.

So, I'll wait patiently. Thank you very much for all your answers, guys.

Might be a silly question, but I tried to take a look at the hangar bay, and the key combo suggested in the manual, RSHIFT+F9, is not working. I can't even find this keybinding in the controls configuration section, although I even tried a repair. Is there something else I should do or is it just a feature that will be added in the future?

Did you tell Jester to tune radio to communicate with the carrier? I tried that mission too a couple of times and I think it worked as intended...

Only MiG-29 (any kind) can have its pylons removed. To do so, you have to select the option "Remove pylon" in the payload screen.

De nada. Me alegro mucho de haber podido ayudarte.

Muy buenas, Mike-Bike. En mi caso, tengo el Thrustmaster T-Flight Hotas X, el compatible con PC y Playstation 3, así que no sé si lo que te voy a decir será extrapolable, o tal vez ya lo hayas intentado, pero te lo comento de todos modos. Con este mando, si pulsas en la opción de asignar eje y mueves un poco la palanca de gases, reconoce el eje Z (así se llama, por lo menos en el Hotas X) y puedes asignarlo. Espero que te sirva de ayuda. Si no, no se qué podría ser. Tal vez alguien que sepa más que yo podrá ayudarte, si esta propuesta no te sirve. Un saludo.

I already purchased Supercarrier module and received also Su-33 module. Every time I start DCS World, I get a warning in Module Manager, telling me that I have a module I haven't installed yet. Only way to get rid of that, AFAIK, and after searching this forum, is installing the Su-33 module, something I consider innecessary since I already have Flaming Cliffs 3, which I bought many years ago. Could ED implement a way to exclude module installation from being warned in GUI once we had checked that? I think it would be useful not only in this case, but also when someone uninstalls some of their modules to gain some more space in disc.

Try deactivating FOD system (LAlt+I) before throttling up. Last time I checked, I could take off from carrier adding that step to what you are currently doing.

I was having the same issue, and I think I found a solution. Go to DCS World Open Beta\Mods\aircraft\Flaming Cliffs\Input\su-27\joystick folder and delete the file T.Flight Hotas X.lua or change its name. After doing that, I recovered my bindings and was able to edit again my device.

Algunos tienen el mismo problema y hay gente que les ha comentado que toquen la configuración de los flaps (imagino que haciendo clic con el ratón sobre la palanquita de la cabina ya vale) antes de intentar subir el tren de aterrizaje... No sé si te servirá de algo, pero no pierdes nada por probar. En mi caso, lo he probado con la misión rápida de despegue desde portaaviones de Caucasus y la tecla G funciona sin problemas...

Once you have activated the option, try to cycle the status bar in cockpit view by pressing lft ctrl+y. That's the way it worked for me. Or at least, I think so.

When creating or opening a mission with the mission editor, you can see a lot of icons in the bar located at the left side of screen. One of this, which looks like the symbol used to represent a switch in electronics schematics, is the one which sets the mission triggers. A trigger is somekind of event activator. For example, shooting down one plane group activates another one, already present in mission. What I did was compare Mig-29 instant action mission with Su-27 instant action one, and edited its triggers to make Hornet group appear after shooting down L-39 group and also make Mirage 2000 group appear after shooting down Hornet group. I think is somekind of bug related with this mission, don't know for sure, but they are saying they will correct some FC3 missions in 1.2.6. Maybe they will also fix that, but it looks like no one else is having this problem. I tried to do my best to explain what triggers are and how they work, but perhaps I missed a lot of useful information. Maybe you should take a look at DCS User Manual, page 59. There you can find a lot of information about mission editor. Triggers are better explained in page 80. And sorry for answering so late. I've been away from home during the last few days.

I also had problems finding the remaining aircrafts, so I took a look at mission triggers. After editing them, I managed to get them in mission. I thought it was something related to my install, because I never saw anyone having the same problem until today. Is there maybe an easier solution for this issue? Thank you very much.