Bravo

I have seen this myself and it seems you have to go in and edit waypoint 0 "Advanced waypoint action" options after you have added the TCN to get it to work.

I found the bug! Its the engine of the missile. It never reaches MACH 4 nor does it sustain Power for very long. The engine performance is more akin that of a SideWinder. Edit: It might be the drag that isnt correct as well, in either case the missiles range is WVR.

So from this we get that they aren't the best missiles in the world, but I have been unable to reproduce a BVR kill with the AIM-7M or AIM-7F from a Hornet yet (Even though I am using the Rift). But I must admit that it might be something I am doing wrong.

I'm using the rift, but I have a Logitech headset for the audio as it is better then the rift. And from what I am understanding from your statement, then I am not able to do this? If such this can be quite a painful feature for many people Edit: Disabling Rift audio in Windows solves this issue. So shouldn't be to much of an issue. But there might be that some want comms on rift and audio on another device.

The whole True North in Caucasus is wrong. it shows straight up on the map as True North while in real life you should be able to track the ruler along the latitude line and that is True North. You will therefor not have the correct correlation between True on magnetic on Caucasus map and it will become more off the further east you go. So in reality this means the the DCS universe is not spherical in the way the earth is.

So my girlfriend could get her own pit instead of using mine, and of course we could fly together

Thread_DCS_External : Fatal Error ! Cannot initialize UDP Server of UR plugin ! (bind): 10048 I got up this error but cant find anywhere in my firewall where it is blocking TS or UR? Nevermind, forgot to add the Lua line as the last line. that was what that stopped it. seems to work fine even with the error above as it doesnt display when launching TS only when re initiating the plugin

Im not sure if I understand your question but, the CDI shows how many radials you are off set course and it is 10 degrees off on the outer dot and 5 degrees on the inner dot which is the only scale it is. Its not a Rnav based system where it goes from Enroute to terminal to approach with cross track error. Hope this help

Hi I have the A-10C, C-101,F-15, HAWK and CA. Since the update Im not able to command units like before the update to 1.5 Im not 100% if this occurred with the change to 1.5.2 or 1.5.3 But right now CA is installed(an I tried to reinstall). But it doesnt work. I can choose JTAC or Tactical Commander at the start of a mission but The button to enter a vehicle is gone, and the litt menu at the bottom of the A-10 map has the ">" symbol but nothing happends when I press it. Am i missing something I should activate? Thanks for the help Bravo

TO the devs: Are there any plan for the C-101 and your future Aircraft to use the nav database that comes with DCS world? It seems very back way around having to update them every time ED does, and possibly ending up with errors vs what is shown in F10 map or mission editor

Do you remember if it was from an A-10 or other A/C?

according to open sources, imcluding http://www.f-16.net/f-16_armament_article1.html Most of the Aim -9 prior to the L used magnetic field proximity fuzes but not exclusively those. the AIM-9L uses a Gallium-Arsenide laserdiodes and corresponding photodiodes that notices when light is reflect back to it. while the later L and M has improved counter countermeasures, this may be why its modelled that the missile continues after passing the flare. But even with ICCM I find it odd that the missile will not recognize flares or other heat sources prior to being launched at an aircraft. it seems to be coded to only be affected by countermeasures after launch, but I dont know and Im curious to if this is the case and if this bug can easily be corrected if this is the case

Hi, Ive been doing some testing with the AIM-9M from an A-10C towards different targets, Flares, SUU-2, M-257, HIP and A-10C. My findings are; Both in 1.5.2 and 2.0.1 The AIM-9M Will find and track the HIP, A-10C and also a already fired AIM-9. The AIM-9M will NOT lock onto flares dropped by the target(HIP, A-10C) prior to launch. The AIM-9M will NOT acknowledge SUU-2 or M-257. In 1.5.2 BUT! if flares are dropped after launch the missile will go for the flares and pass straight through them. It wont hit the flare and explode but continue straight and hit the ground. in 2.0.1 I observed something different, Im not sure if the code is new or not, but my guess is that it is a little different. The AIM-9M would after launch track the Flares and after passing the flare change course drastically for flares dropped by FW, while start diving towards the ground when passing flares dropped by RW. There was a TV show that aired a couple of years ago on TV where you could see an RNoAF F-16 fire an AIM-9L at a flare where it hit and exploded near the flare. Im not sure if this is the deal with AIM-9M but I am curious to if you have some comments to this? I noticed that in 2.0.1 It will track the Sun which I think is Awesome. I did not test this is 1.5.2 I believe, that pending on the seeker head the angle towards the sun it will be able to track a target vs the sun will be different. This I have not tested as I do fly anything else that can fire other missiles(Not known with how the SU-25 works, so not tested) But when I steer the seeker towards a Flare, SUU-2 or M-257 it is unable to acquire them. Seeing how the AIM-9 track flares after launch why does it not acknowledge them prior to launch? If locked onto a aircraft and the computer logic says follow the movement, OK but this seems so complex I doubt it true, then you should have the logic in the missile and not in the aircraft and thereby it should not track flares the way they what it does even after launch. If it sees "profiles" that looks like aircrafts, the same should be true. It would ignore flares dropped unless then look like the profile of an aircraft. but also lock onto flares with "profile" prior to launch. And when the flare, SUU-2 or M-257 is the only heat source it sees it should acknowledge and track it as well should it not? These sources are just a extremely tiny sun or just another heat source like the fumes from a aim-9 already fired? Im not a engineer or have that much insight but logically I am wondering if this is a bug, not implemented at this time or to classified to modell? To te ED team, Thanks for making a awesome simulator for us!

Hi, I was wondering if you would be willing to do some changes to some of the navaids when you are going to update the Caucasus map. Giving the the VORs which have DME in real life a paired DME. Setting up DME stations with those ILS systems which have their own. Giving the possibility for aircraft so set TACAN to the paired frequency of the DME or VORDME to recieve Range information from them.(not bearing) and giving them the real name. Kutaisi VOR/DME KTS (and renaming the Kutaisi TCN to KOP as its not in use in the world) Tblisi VOR/DME TBS Give the ILS different identifiers for each; Vaziani has the same identifier for both direction but with different stations Also I was wondering if you would be willing to increase the Glide slope into RWY 13R at UGTB With the current obstacles on the approach it would require a 3,5 degree glide slope per TERPS criteria. (140 ft clearance) The ROC(Required Obstacle Clearance for the TERPS, but Im usure if it accounts for GS offset from THR) Im not sure on PANS-OPS yet as Im having trouble deciphering how they calculate the Obstacle Clearance Height/Altitude on the ILS as I do not have access to the right document. But my best reworking of the standard 3 degree glide slope combined other PANS OPS I found helped me come up with this; Criteria gives me a 3,7 Degree glide slope and a obstacle clearance of the trees at 0.9 DME from the threshold with a clearance on the glide slope of 160 ft vs the current 3 degree glide slope and 98 ft clearance. Also if it would be possible to move the Localizer part of the ILS system to the end of the runway you are flying into, and not at the start as it seems like it is in the mission editor. I was wondering if anyone here has the design criteria for the Russian approaches in English? My goal is to make approach charts for as many airport as I can that will work with the standard DCS to help give player more immersion in the game. They will be free and I will try to update them as changes are being made If someone can explain more to me how the LUA code and rules for them work I would be more then happy to help update it. I can currently change name and frequencies on the ones that are already in the Beacon.lua but I dont know how to add DME or the russian types of stations. Or to be honest, I dont really understand LUA but Id like to learn enough to help.

You can also get some of the Georgian approach plates from Eurocontrol but they would be way off. Im currently making some plates but it is going to be some time before they are released. This is mainly because it takes me long time to make each one and they are more oriented towards how my group flies and the use of human ATC with dedicated frequencies. If you want to test them and see what you think of them, send me a PM.

Im sorry that was not my intention it was an invite to you to come fly with us with your group we fly with many other wings as well. Ill moderate away my earlier post

Hope you have fun and happy flying Cheers Bravo

Got gateway timeout when i tried to click on the paypal link

Hi, I was wondering if there will be a fix for Lochini airport concerning the misalignment of the runway and naming of taxiways? I noticed that the magnetic heading on the runway is worng, its indicating 121M in the game when you line up and with a magvar with 6E thats going to be 127T while the AIP of Georgia says its 136,54T and 5E should give a Magnetic heading of ca 132M. for runway 13R/(31L is 316,56T). Also the 31L ILS is correctly labeled INA but I could not get the DME associated with it to work, for TACAN equipped A/C they should tune CH 26X to get the paired frequency for LOC 108,9MHZ (GP 329,300MHZ). But the ILS 13R is also labeled and identified by INA, while it should be IVP. with Frequencies 110.3MHZ (GP 335,0MHZ) and DME on the TACAN CH 40X. DME stations location is paired with GP positions. A civilian A/C or non-TACAN A/C should read DME when tuning the paired VOR/LOC frequency.