wernst

Unfortunately the Hornet sim has quite a few major bugs or open issues to be solved, these may ruin the feel of the game. The “NWS business” is the first minor bug and it surely won’t ruin my feel of the game at all.

OMG . . . yes AD, if people start complaining about issues like “NWS HI isn’t simulated correctly” leads to the conclusion, that all major systems of the hornet are already simulated perfectly and only minor issues have to be solved. AD, you’re 100% right. Let the ED team solve real issues and don't let them get headaches from nullities.

Everything is fine now, the ICLS/ILS mod is working well. I did an ILS approach to RWY 12L at Dubai Intl. According to the JEPP ILS chart for RWY 12L the final glide path approach segment begins 5.9 nm before threshold, at the final approach point (FAP). In the sim the glide slope bar appears 6.1 nm before threshold, perfect. The entry ALT of 2000 ft is mandatory at the FAP. Flying this altitude constantly the glide slope bar moves continuously down as becoming closer to the RWY - checked. According to the ILS chart the localizer (ILS DME 110.1, IDBL) can be received at a distance of at least 12.1 nm. In the sim the localizer bar can be received long before, namely at a distance of about 20 nm or so - checked. I was misled in my early findings that the glide path coverage should also be to a distance of 10 nm, which could be but at some airports but is not always standard.

Yes, looks good. I'll repeat your test at DUBAI with an 12L approach at two constant altitudes: 1. constant 2000 ft: bar appears 6 nm before threshold and moves down, as has been shown clearly 2. constant 3200 ft: bar should appear 10 nm before threshold and should move down constantly while approaching. As ILS standard the glide slope bar is usable to the distance of at least 10 nm. And it often has been certified for an extended service which exceedds 10 nm.

I'm looking forward to your findings. I still hoping that I'm doing something wrong because I truly love the mod ILS capabilities for the Hornet.

The last two updates .2115 and .21235 have overwritten the modified “Beacon.lua” file with the DCS standard beacon file. No real problem, the mod file can easily be restored. The glide path slope bar is simply not working, it has no function as an ILS GP indicator. It first appears when less than 5 nm miles close to the RWY although entering the 3 deg ILS GP sector more than 10 miles before. The GP slope bar stays with constant distance always a little above the velocity vector and doesn’t move even when rough altitude changes are made. It moves down or up as the velocity vector moves up or down as it would be coupled to the velocity vector. This doesn't make sense. The localizer bar is working as it should be for ILS RWY heading.

Ich bin ex Pilot (PPL-A, C) und fliege nur noch virtuell in DCS. Ich möchte jetzt in die VR einsteigen und denke an eine Oculus Rift. Wer fliegt im Raum LR / OG / FR mit dieser VR Brille und würde mir eine kurze (1/2 h) Demo geben? Fast alle Piloten, die mit VR Brille fliegen, sind vollauf begeistert. Ich habe keine Idee, was man wie sieht und würde mir gern selbst vorab ein Eindruck verschaffen. Ich wohne nahe LR, im Großraum FR / OG. Bitte eine „private message“ schicken, wenn ihr mit helfen könnt. Danke im Voraus.

Thanks, as proposed I tried different SSAA settings and got the following fps (under identical mission conditions): SSAA off: 45 - 55 fps SSAA 1,5x: 25 - 40 fps SSAA 2,0x: 18 - 25 fps In all settings the CPU load was not higher than 30% and the CPU temp. did not increase over 60 deg. C. What I learned from this test, pls correct me if I'm wrong. When replacing my 1920x1080 monitor for an ultrawide 3840 x 1080 version 1. I should expect a significant but just acceptable drop in fps. (with the GTX 980) 2. Surprisingly the increase in CPU load and CPU temp is barely noticeable. 3. As consequence: The GPU power is mostly relevant for the 3840 x 1080 monitor performance

Are there any restrictions, limitations or (visual) drawbacks when playing DCS 2.5. on an ultrawide 3840 x 1080 monitor? Which? My actual system has a GTX 980 with a CPU which delivers in average 50 - 60 fps on a 1920 x 1080 monitor. (single player, free flight missions, settings to HIGH) Which performance (fps - wise) can be expected when switching to a 3840 x 1080 monitor? The number of pixels for the GPU and CPU to process is then double. A rough estimate tells me that the fps performance would be half and the CPU load would be double? Could that be? It’s probably not as simple calc as this, that’s why I’m asking for your experience here. Thanks

Yes, you and Impalor, Sandman1330 and Bitmaster, you all are fully right. I uninstalled the cooler and fan and could see easily what was wrong. The lamella of the cooler unit were full of dust. And even worse, the thermal compound wasn't covering the heat sink area fully anymore and looked badly deteriorated. And, I have the impression that the fan was per design a bit weak (28 m3/hour air) Conclusion: bad maintenance, shame on me. It's a miracle how my trusty old i7 920 could survive so long in hellfire. Thank you intel, this CPU has passed a cruel long term test successfully. Action: A new cooler will be installed, NOCTUA NH-U9S with fresh thermal paste. I was misguided by looking at the CPU load only, which was never exceeding 35%. But even low load can be harmful when the heat isn't dissipated properly. Now it's the question how long the CPU still lives after the "refreshment". ----------------------------------------------------------------------------------------------- Edit: System: intel i7 920, GTX 980, 16 GB RAM, Samsung 500GB SSD 950 EVO DCS 2.5: free flight missions only settings: HIGH mon. res.: 1080p 10 years old CPU cooler: amb. Temp: 23 deg. C CPU load: max. 38 % CPU temp: max. 85 C New CPU cooler Noctua NH-U9S with fresh thermal paste installed amb. Temp: 23 deg. C CPU load: max. 38 % CPU temp: max. 61 C

I wonder which generation of PCs is really needed for running DCS world 2.5 with decent fps. Which PC component has to be up to date, the CPU or the GPU, or both? I have a 10 years old intel i7 920 with 16 GB DDR3 RAM together with a 3 years old GTX 980. Most of the time I’m playing DCS single missions or free flight missions with system settings to HIGH. Under this conditions I can see in average 65 fps, but not less than 50 fps, with all modules and in all missions. Under full load the CPU heats up to max. 85 deg C (no OC). I'm a little worried that the CPU gets too hot, continuously. But the Win task manager surprisingly shows for CPU not more than 35% load. Could this be true and real? As consequence I ask myself: In which respect could I benefit from upgrading my trusty old i7 920 to the latest generation of CPUs, e.g. intel i7 8700K? (with new chipset MB and DDR4 RAM). I assume that the latest CPU will run cooler under full load, probably well below 75 deg C. But, besides VR, what else could be improved with a major CPU update?

First of all, thanks again for the work, it's more than a mod, it's a truly useful upgrade. But my first experiences with IFR approaches using these dedicated ICLS beacons in the PG scenery are kind of mixed. ILS approaches are now working in PG, but there is a "but". The localizer bar is visible as early as it is real. Fine. Good for early fine tune of heading. But the glide slope bar display appears very late, about less than 5 nm close to the RWY threshold when being on a 3 deg glide path. Furthermore, the glide slope bar display is very insensitive to pitch corrections. It doesn't respond as I'm used to with other DCS ILS approaches, e.g. with A-10C. The closer one gets to the RWY the more sensitive is the response to any corrections made to heading and pitch, which is logic and normal. But the glide slope here responds very slow even when almost 1 nm close to the RWY touchdown. As consequence, I've difficulties to stay on the safe glide path when guided by the glide slope bar. Any corrections made for a safe altitude are too late for a safe landing on the RWY threshold. Do I miss anything?

When building a new mission in ME and choosing “RWY takeoff” only the same fixed RWY heading will be allocated by the ME, even if the field allows landing and takeoffs in both directions - and regardless of wind. Is there any way to change this given RWY heading to the opposite in the ME?

My TM Warthog throttle unit has one slider as analog input control - only. Especially for the Yag-52 I wish I would have more analog input capabilities, at least three for the most important functions: 1. wheel brake (the brake is very/too responsive when digitally on/off controlled only) 2. elevator trim wheel 3. prop pitch setting Of less importance are: 4. oil radiator flap 5. engine cowl flap Is there any additional hardware, e.g. USB modul available with 3 oder more analog inputs (wheel- or slider-type)?

great, great plans. Looking foward to install these ICLS beacons for the Hornet. Where will you post/publish theses new beacon.lua files? Under which forum? I don't want to miss these new goodies when they are out.

Thanks, just a second ago I tried the ZIP download and it worked. Beacon.lua is installed and looks perfect. This mod is by far the most valuable extension for the Hornet. It provides ILS functionality to ground operation as does have the Hornet in many countries. I love flying IFR in low vis weather and enjoy the feeling when down safely. I dare not to ask: Could you think about making such a list for the Caucasus region? I could think of two Beacon.lua files, one for the Hornet and the original for the other planes, e.g. A10C. Keep up the good work, thanks a lot.

Yes, your Beacon.lua file which I downloaded looks weird when opened with editor. Obviously faulty download. Sorry, I have to ask again: How do I download the Beacon.lua file from Github in the right way? Simple right click on it doesn't work well. Do I have to install any Github GUI? Do I have to sign in? Your help is highly appreciated, because I'm keen on getting this ICLS to ILS utility. Thanks

again, it's a great job, you've done. Thank you. ED should have done it. I'm not one of the ungrateful people who find always hairs in the soup. But what I found is that after installing the Beacon.lua file the ME doesn't show any beacon symbol and the ILS approach sector symbols (triangle) in the map anymore. Did I miss to set some switch or setting?

thank you, great work. Again, another stupid question. How do I save the Beacon.lua file from Github. Do I have to sign up or have to download any Github GUI? UPDATE: I was able to downlaod the lua file.

Thanks, drPhibes, your simple modification gives highly useful results. Maybe a stupid question, in your first post concerning ICLS to ILS you said: "If anyone is interested, I can post a short "how to"-guide (NOTE: Not IC compatible)." What is "IC" ?

Thanks Brun - to be honest, up to now I've never looked into the GAMEPLAY folder because I had (wrongly) considered this folder to be for playing GAME mode only.

"Easy Comms" ? Where? Which menu?

confirmed. At BATUMI I got ATC contact with 131,000 input to :AM selected.

pls note that I'm having this issue in SP mode, didn't check MP.

I’m getting even more confused. Under the Control Option Menu I have assigned: “COMM Switch - COM 1” (which has keyboard default “RAlt+\”) to my throttle switch 17 (as an example) and “COMM Switch - COM 2” (which has keyboard default “RCtrl+\”) to my throttle switch 18 (as an example) After entering the FM FREQ via M dial to UFC COMM1 or to UFC COMM2 I’m then using my switches 17 or 18 to recall “Communication Menu” (which is usually avbl under the keyboard key “\”) No radio response. What is wrong here? What is the catch? I'm not complaining if this is an early access issue, it would be fine with me. I just want make sure that I haven't done anything stupidly wrong.