Nereid

No this won't work because the VHF 2 operates between 30 and 76 MHz. 30,000 KHz should be ok, it's 30.000MHz and this is actually working with VHF radio 2. :) 124,000 KHz (124.00 Mhz) won't work with VHF radio 1 and I can't see any reason for this. But that is the other part of the story. The text message "bomb hit" sould appear anywaybut it won't. Not if a Mk82AIR hit's the zone (and the trigger is detecting this) and not if a BDU-33 is in the zone. If you change the trigger to "player in zone" (or anything like that, I'm not at my PC in the moment) it works, i.e. the text appears and the radio message is send. But "bomb in zone" won't work - at least not this way.

Just a funny glitch: If you fly upside down a bomb (BDU-33 or even a Mk-82) will fall trough the wings without doing any damage.

Thank you. But it's currently a very simple approach. At first I just wanted some audio feedback, when I hit the zone with a training bomb (BDU-33). BTW: The radio message wont work at 124000 Khz either. I couldn't get it to work with the VHF radio 1 (tested it with another trigger). It works at 30000 Khz with VHF radio 2. A10-C Weapon Training Bombs.miz

I can't get this to work too. Tried BDU-33, Mk-82, Mk-82AIR. Trigger type "once" or continuous. Radius of trigger zone 100 up to 1000. It won't work. A bug?

I'm not quite sure if this is a flaw, but using the LUU-2 with a SUU-25 dispenser the flare containers are just dropped as normal bombs (and appear just magically under the dispenser). Should they leave the dispenser at the rear (there are four holes in the rear of the dispenser).

Well... I have tried Softth a few months ago and it didn't worked for me. Now I'm using helios with a second screen and tried to give it another chance: Softth 2.08 alpha. Ok, it's alpha but for some guys here it seems to work. At least I got it to work, but again it's unusable for me. My options: fullscreen, resolution 3820x1080, exports to the right. First the render quality: Well, it's mediocre at best. The screen resolution is ok but it looks like an 1024x768 resoultion just scaled up to 1920x1080. It's all a bit blurry and there is no visible sign of AA. Second: In windowed mode without softth all cockpit instrument exports works flawless. in fullscreen with softth the second screen is just plain black, i.e. none of the exported cockpit instruments is drawn. My Softth-Config: Any ideas?

Yes. A yellow handle between his legs in the Huey means that he is rather kind of sick. :clown_2:

I'm using the Fighterstick, the CH-Pedals and the CH Pro-Throttle for severals years now. Nothing broke, nothing to complain about. The Fighterstick has the very minor issue, that a diagonal movement of the stick is not very precise, cause the two axes are forcing you into one axis a time a bit. But it's hardly noticeable. I'm also using other stuff von CH: the Throttle Quadrant and the Multi Function Panel (MFP). All products works like charm out of the box. The software is a bit old fashioned, but ok so far. To be honest, I'm thinking about the Thrustmaster Warthog as a replacement. But i'm not sure if or when I buy that one.

Nice tip. :) But I will have to ask for permission to publish a map as a private user. As far as I understand their licences, it's permitted. But I will ask them to be on the safe side.

How do you translate TACAN to MHz?

Well, the other list includes them. But I think we need a simplified map of the region at least with airfields, main cities and the NDBs to be useful. Perhaps I will add this in the next few days. I have created the list for myself and merged a document containing all Airfield diagrams and the list of NDBs (above in this thread) to include the most important information of all airfields, so I can upload this to my smartphone as a reference in flight. BTW: I have not included all NDBs of the other list, because some of them seems to be incorrect. And if you find incorrect values in my list, feel free to tell me. ;)

Yes. The second page is some kind of a mistake. The damn export had included it, dunno why. Its a work in progress. There are other NDBs around and i plan to include them also. But at the moment I don't think this will be very usefull without a map. PS: Document is fixed. Thank you.

First switch on the NAV radio and tune in the VOR frequency. Then set compass indicator to VOR mode (upper left switch). I have found these VOR freqencies so far in DCS: GELENDZHIK: 114.3 MHz KRASNODAR CENTER: 115.8 MHz KUTAISI: 113.6MHz MINERALNYE VODY: 117.1MHz TIBILISI - LOCHNI: 113.7MHz My own list for frequencies: http://nereid42.de/dcs/DCS%20Frequencies.pdf PS: Hmmm... did you mean TO/FROM headings as functional in modern aircrafts? Well... then I didn't get this to work also. The compass indicator seems to be only working as a pointer like NDB navigation. I don't know if the real think also gives only the direction. The correct frequencies where my main problem to get VOR to work at all.

Hi! I have created my own list as a pdf: http://nereid42.de/dcs/DCS%20Frequencies.pdf It includes all airfields (hopefully) with Coords, elevation, TACAN, tower/ILS/NDB/VOR frequencies and morse code for NDB (if known so far).

The question is: Why have a game fm at all. :prop:

Well, i have never tried the game filght model so far, but I thought similar at the beginning about the sim flight model. "Puh, this is hard", "I will never learn to land this thing" etc. But after about one, two days of training (distributed over a couple of days witj about one or two hours of flight) I finally got it. Not perfect, but you will have to get the "feeling" for the amount of input and this will take a while. It's like learning to ride a bicycle or a car. If you have to think what to do, you will crash often (hopefully not in a car ;)). But at some point all control inputs are just done instinctively. And adjust the axis curves to your preferences. For me a user curve for pitch, roll and collective (!!) was best.

Ah! :doh: Thank you alot. I was stumbling over the same issue the last two hours, just trying "\" without success. And then it's so simple (but maybe a bug). Ok, comm with ATC now works. But I can only communicate with the ground crew by opening the cockpit doors. Maybe thats the only way, but perhaps I'm missing something.

Yeah, I was thinking the same. But I decided to buy it just to support the 3rd party developers. I flew only once so far but it looks nice. And well... the loading times for a mission in DCS World are a BIG improvement now. No more waiting for about a minute to start - just a few seconds. Great job. :)

I'm not quite sure what "long load time" means, but I have noticed a very long load time when I start a mission and I have installed DCSW and all modules on a SSD also. I can't measure it right now, but it takes about 60 to 90 seconds until the simulation starts. Prior to 1.2.0 I remember much lower load times.

I have checked this and noticed this behavior also. Its impossible to change the view with the mouse after opening the briefing ingame. Keys still work but no mouse.

I have noticed this also. But then this lamp should be lit before start, but I had never seen it yet. I was stumbling over this when I was checking the startup procedure in the manual. It seems to be a minor bug.

In chapter 9 of the manual it says: "Upon reaching normal oil pressure in the engine gearbox, the green “Р масла ПРИВОДОВ” (gearbox oil press norm) light will illuminate." (located in the left overhead panel warning and advisory lamps) Well, perhaps I do something wrong but this light will never illuminate in my startup procedures. Is this lamp not functioning in the actual sim?

Signed. ED give us NATO symbols in the in-game map (F10) please. :)

And suddenly it's back. Cant click anything without Alt-tabbing prior. Doesn't matter if Aero Interface is disabled or not...

Well... it seems, I'm not alone. :) Also updated to 1.2.1 (from non DCS World) yesterday and for each mission i can't start the flight with the mouse (only with the keyboard) and I can't leave the mission because it's not possible to click on the "quit"-button until I use the Alt-Tab workaround. I also can't click on any cockpit instruments without alt-tabbing first. After alt-tab and switching back to DCS anything works fine. Win 7, 64 bit. Fullscreen (only one monitor used at the moment, not altered any config file yet) Update: After unchecking "Disable Aero interface" all works fine now.