Phaëthon

Unfortunately I didn’t save the track. I did however make a video illustrating what I believe to be a fairly easy thing to recreate: an F16 carrying Mk82’s HD and trying different CCIP/CCRP releases. Although the video only shows one example for each, I did make several attempts and they were always consistently missing by the same margin. Tomorrow I can do it all over again to provide a track, but I feel you can easily do it yourselves.

CCIP/CCRP and Toss missing targets by hundreds of feet. Documented the issue with the following video: Please let me know if this an issue with the latest patch or if I'm doing something wrong.

Edit 1: CCRP line also suffers from the same issue.

Just updated to DCS Open Beta 2.7.7.14727. Experiencing an issue with the F-16C CCIP Bomb fall line flickering and jumping all over the place. After a while it seems to stabilize. I'm uploading the track file and also recorded a video for you to check it out: CCIP bomb line flickering.trk

Mine also opens in the bottom right corner. Check if my suggestion helps anything and report back, I'm curious. If you need me to try something don't hesitate to task.

The reason why I suspect it has to do with multiple monitors is that when I went to test it in DCS, I wasn't on the computer which has the installation, so I did a remote access (which changes resolution) and the NS430 window didn't pop-up (or maybe it did but out of canvas). Then I went to the computer and tested locally and all went fine. I think it would be worth the try to check if with a single monitor + dcs set to fullscreen + set to the native display resolution makes any difference for you. I'm betting the window is being positioned in some weird coordinate. But that's just me guessing..

Yep, can confirm it works fine. Check if you are running DCS with multiple monitors, it's probably being drawn outside of your main one, if that's the case.

Hello, which pop-up window? Edit: sorry, didn't see you were referring to the NS430, will check it out and report back.

Hello, quick question: I always liked the C101 module, but it used to feel slow and easy to stall (not saying that was a problem, just that it was how I remembered it). But I tried it again today and although the pedals tremble to warn you of imminent stall, you can actually pull that stick back as hard and long as you want and the plane not only doesn’t stall but gains actual speed. Even when I have the throttle around 75/80%. Was there any change in the flight model? Is it accurate like this? (The C101CC)

I haven’t tried MP, but can confirm these issues in SP. Normally these effects when triggered appear in SSA’s verbose log, but the ones I mention don’t even register there. The landing gear effect you can fee it’s wrong even in f1 view, the lg indicator in the instrument panel already shows the gear in/out but the effect stays playing for some extra 20/30secs. However I’ll check it the wing movement once again and report back.

I'd like to report some issues I've run into using the F14-B and Simshaker, and ask if there is any solution: 1- The Landing Gear (in/out/lock) sound doesn't match the in-game event. While the gears take little time to deploy in-game, the sound/vibration stays for a lot, lot longer. 2- After an Eject event, Simshaker stops working (program still runs but no longer triggers any sound) and has to be restarted. 3- Failure/damage effect not triggering. 4- Flaps movement effect not triggering. 5- Refuel boom vibration doesn’t quite match the boom in and out points. 6- Wing movement effect not triggering. 7- Also, a suggestion that I would love to see implemented if possible, would be a TEST button next to each item in Simshakers list of sounds, so that it's easier to test the sound and fine tune the volume without having to jump into the game and recreate the event every time.

@havok2brilliant work, exactly what I was looking for, thank you so much for it! However I have downloaded the latest DOF.fx and it doesn't appear to work, can you confirm if it's compatible with the latest Openbeta? Cheers! edit: sorry! for some reason it wasn't working but now it is, all good!

Damn, now THAT is public service! Many thanks once again! Cheers!

Thank you thank thank you! It's probably one of the most well designed and comprehensive set of information currently available in user files. I have two suggestions: - Is it possible to include the airport's elevation in meters, as you did with Caucasus? - Is it possible that the numbering on the left column (or adding an additional column) correspond to the FC3 airport IDs? Kind regards

Does it have to be placed in the game root folder or is there a way to make it work in the savedgames folder? Just to prevent it being overwritten every time the game updates/repairs.

@Sérvalpilot has just taken matters into his own hands and posted a working solution for the reflections issue. Check it here:

This. I've been begging the devs on discord for ages for this. Thank you sir, you made my day!

This! I feel it suffers from the particular stigma of being a free aircraft and not deserving/justifying the man-hours in polishing it. Hopefully I'm wrong.

Here's a list of a couple of visual issues that I came across in Su-25T (DCS 2.7.1.7139 Open Beta) 1) Cockpit glass reflections are still TOO strong. Very often it's almost impossible to look through the HUD. 2) What is being reflected in the cockpit glass is totally wrong (impossible perspectives and whatnot). Being a low fidelity module it's understandable, but still.. I'd rather just have it off instead of reflecting the joystick+instruments on the HUD. 3) Instrument light is very very dim if it's dark outside (ex. Overcast) but still daytime. It appears it only gets properly lit if it's actually night time. 4) HSI instrument light is much dimmer than all the rest. 5) Bindable Flashlight key but without any effect. Probably the same for all FC3.

That would be great, couldn’t find it either and it’s not as easy to search as I would think. Once again, thank you

It would be wonderful if you could point me to it! Thanks!

Hello, I am gathering a list with the the playable planes and helicopters in DCS and wanted to ask your help to complete the following table with the Generation and Date of introduction of the specific model DCS uses, since many of the modules are modelled after later versions of the aircrafts. The First Flight and model Introduction was taken from Wikipedia and refers to the base models, but if there is some correction to be made or some module missing don't hesitate to say. I'll update the table with the information on your comments. Thank you! Module Gen First Flight Introduction Model Date Bf 109 K-4 Kurfurst WWII 1935 1937 Fw 190 A-8 WWII 1939 1941 Fw 190 D-9 Dora WWII 1939 1941 I-16 WWII 1933 1935 P-47D-30 Thunderbolt WWII 1941 1942 P-47D-30 (early) Thunderbolt WWII 1941 1942 P-47D-40 Thunderbolt WWII 1941 1942 P-51D-25-NA Mustang WWII 1940 1942 P-51D-30-NA Mustang WWII 1940 1942 TF-51D Mustang WWII 1940 1942 Spitfire LF Mk. IX WWII 1941 1942 Spitfire LF Mk. IX CW WWII 1941 1942 A-10A 1972 1977 A-10C II Tank Killer 1972 1977 A-10C Warthog 1972 1977 AJS-37 Viggen 1967 1971 AV-8B Night Attack V/STOL 1981 1985 Ka-50 Black Shark 2 1982 1995 C-101CC Aviojet 1977 1980 C-101EB Aviojet 1977 1980 Christen Eagle II 1977 1977 F-14A-145-GR Tomcat 1970 1974 F-14B Tomcat 1970 1974 F-15C 1972 1976 F-16CM bl.50 Viper 1974 1978 F-5E-3 Tiger II 1959 1962 F-86F Sabre 1947 1949 F/A-18C Lot 20 Hornet 1978 1983 J-11A 1998 1998 JF-17 Thunder 2003 2007 L-39C Albatros 1968 1972 L-39ZA Albatros 1968 1972 M-2000C 1978 1984 Mi-8MTV2 Magnificent Eight 1961 1967 MiG-15bis 1947 1949 MiG-19P Farmer 1952 1955 MiG-21bis 1955 1959 MiG-29 1977 1982 SA342 Gazelle 1967 1973 Su-25 1975 1985 Su-27 1977 1985 Su-33 1987 1998 UH-1H Huey 1956 1959 Yak-52 1976 1979

In the meantime I’ve also ran into an issue that setting the radio frequencies in the mission editor preset channels doesn’t change any of the presets in the aircraft. The exact same issue appears in a video by the Gream Rippers at 3:04: https://youtu.be/nAZ6o7g8cBU

@Hiromachi thank you very much for your attention and forwarding to the team. Keep up the good work! Cheers

I am reporting the following bugs and issues with the Christen Eagle II, currently on DCS 2.5.6.58125 Open Beta: a) An audio glitch sounding like a buzz saw can be heard when clicking the hotas buttons (or keyboard keys) assigned to: Canopy Open and Canopy Close Canopy Lock and Canopy Unlock Radio channel switch and Radio flip flop switch Accelerometer reset b) Both cockpit lights are unassignable in the controls. c) The Aerobatic Sight Device's upwards movement isn't limited by it's physical limits. Although the model doesn't move more than it should, when adjusting down after extending upwards past the limit will result in a delay before it actually moves. The delay is longer, the longer it moves virtually past it's upper limit. d) Fuse On/Off binding only turns the Fuse On. Doesn't revert to Off. e) Assigning the following commands (Radio On, Radio Mhz +) to the Thrustmaster T16000M Throttle Button 7 doesn't do anything. However assigning to another button works. Also, Assigning the Radio Khz + or Volume + to that button works properly too. It would be great if @-Rudel-, someone from Leatherneck or ED could check this issues. Thank you!