DigitalEngine

Is @Wags indicating it will be 2-3 more years before we see the Vulkan API in DCS World?

"that may change in the future. "

Bumping this, hopefully with the new AI / flight model this will be added.

As a very late update Solution, works as intended. The Su-25T uses the PRMG system only. AFAIK, only Russian military airfields have the PRMG system, and only the following, at least the last time I checked. Krasodor - Centre, PRMG 38 - *Runway 09 Only Krymsk, PRMG 26 - *Runway 04 Only Maykop - Khanskaya, PRMG 36 Mozdok, PRMG 22 [*Must be the active runway!] And of course as the Su-25T being a Flaming Cliffs type DCS module, one dose not select the particular PRMG frequency, but only selects the landing sub-mode. For additional info, PRMG notes here, and Russian PRMG & ILS Landings post.

I had this issue also, however, I had the same issue when setting up a simple test flight mission. I solved it by swapping out my Joystick and throttle USB ports. (CH HOTAS setup).

Not sure were to post this. The DCS User manual need to be updated, specifically in regards to the OPTIONS settings. With the new options of the Anti-Aliasing, Upscaling options, the Upcaling slider, Sharpening slider, etc, etc... What these options do, how do they work?

Thanks @Ironhand, interesting, yes, if you do get your hands on such, let us know please.

@BIGNEWY, could you double check this please, maybe something "got lost in translation"? Seems really odd for an aircraft landing lights alignment to be offset horizontally to the left (or to the right). Maybe the team member though we were referring to the vertical offset, which has two settings on the DCS Su-25T. Thanks.

For whomever may be interested. This is a Export.lua for the sole purpose of exporting the dcs mission (accumulated) time to a port/socket in one second intervals, as a whole number value. function LuaExportStart() package.path = package.path..";"..lfs.currentdir().."/LuaSocket/?.lua" package.cpath = package.cpath..";"..lfs.currentdir().."/LuaSocket/?.dll" socket = require("socket") IPAddress = "127.0.0.1" Port = 31090 MySocket = socket.try(socket.connect(IPAddress, Port)) MySocket:setoption("tcp-nodelay",true) end function LuaExportBeforeNextFrame() end function LuaExportAfterNextFrame() end function LuaExportActivityNextEvent(t) local tNext = t local TIME = LoGetModelTime() -- "%.0f" displays the data in whole seconds, with no decimals. socket.try(MySocket:send(string.format("Time: %.0f \n",TIME))) -- The below writes the data in one second intervals. tNext = tNext + 1 return tNext end function LuaExportStop() if MySocket then socket.try(MySocket:send("exit")) MySocket:close() end end Thanks to @JaBoG32_Dirty, his YouTube Channel "DCS Flighttraining", and his github repository "DCS-Export-Server-Simple". JaBo has a simple TCP DCS viewer with with which you can view the data in real time. Next step, if someone will please help me, is I want to import the data onto a html webpage file, use AJAX, and then format it into a 24hour time format. For example, if the mission starts at 0600, add the accumulated mission (120 seconds) time and display it on the html page as 06:02. Could anyone help me with such a JavaScript code? I've done something similar using data wrote to a .txt file, shown as a static example here, and here.

Here is a CH HOTAS map for the Su-25T with SRS support I've created, for anyone who might be interested. Su-25T CH Products HOTAS Map files Zip

No, this is a bug, introduced earlier this year, I think. In VR the landing lights are noticeably off center to the left. Could this bug be put on report please?

The Su-25T Cockpit View Flash Light is inoperative. Could this please be put on report? Flash Light Test.zip

This bug is still present. If doing a very hard landing, where all tires are blown, there is no sound of such in the cockpit, which should be, and used to be. The below video displays/explains the missing sounds bug. Could this bug be put on report please!

As per the title, the Su-25T landing lights in "high beam" are off center to the left a few degrees. In VR mode, it's noticeable enough to actually induce VR nausea on taxing at night/early morning (for me, anyway). Plus, for one of the "free showcase module" it does not show much attention to detail, to say the least. Could this be put on report please? I know I saw a quick fix posted for this (editing a lua file) at one time, however, after several searches can't seem to find it, and if I remember right, the fix would cause a integrity fault anyway.

That I don't know MAX, however, I think if I had this issue, even though it'd be a pain, only way I'd konw to fix it, is to remove all mods, do a DCS clean/repair/ rename the Export.lua file, clean the saved games scripts folder, uninstall VA and VIACOM, basically do a complete uninstall and reinstall/setup. Thanks Hollywood, realizing your time resources are likely limited, so, I'm not really requesting this, as much as asking if this is feasible. Would it be possible to write some type of "script layer", such as, if you are in a FC3 module, and you are using the SimpleRadio Standalone app with VIACOM, that to contact ATC, the active SRS radio must be tuned to the correct ATC frequency, or the request would be filtered/blocked, simulating selection of the correct frequency as imperative? Same for commanding the AI pilots?

OK, so back to the original issue/question, as in the quotes below. I'm now suspecting this is a core of DCS FC3 module radio communications limitation, as it were. Could Hollywood chime in on this please? :)

Max, no I'm not having that issue. I just did a quick test, "request start-up" to Mozdok ATC in the Su-25T, the VIACOM Configuration Window PTT tab indicates that I'm transmitting on TX1. Got a reply back from Mozdok ATC. However, my SRS R-862 radio was set to frequency 124.00, where as the Mozdok ATC freq. is 137.00. You have to use the SRS Overlay to change FC3 freqs. or set up custom controls on you HOTAS or keyboard.

Max, As far as I can tell, VAICOM, with latest versions DCS/VA/VAICOM, is working as advertised for me, as far as sending/getting commands from the ATC, other than with the FC3's "internal radio" seeming to TX/RX to on all frequency's at once (that is, to AI entities). I now suspect this is a core of DCS FC3 radio communications limitation, as it is. I haven't worked with Lt.Bot (AI pilots) yet. Maybe Hollywood could chime in on this please? :music_whistling::helpsmilie:

Thanks Max, I'm not asking how to tune the radios in a FC3 + SRS aircarft, that I can do with the SRS radio overlay, and speak (or not speak) to other warm blooded clients just fine. What I'm referring to is this, for example in the TF-51D, to contact Mozdok ATC; One must preset one of the channels to frequency 137.00 in the M.E. (let's say channel 2). Then one must select that channel (2) on the aircraft radio control panel in the cockpit in order to talk to Mozdok ATC, otherwise Mozdok ATC will not hear you, as you are not transmitting on frequency 137.00. However, with FC3 aircraft (for example the Su-25T), and using the SRS Radio Overlay to select let's say frequecy 124.00 (or any frequecy, for that matter), the Mozdok ATC will hear and respond, even though the Mozdok ATC should only hear me and respond on frequency 137.00 (VHF, that is). I do have DCS Easy communication unchecked.

Using the Su-25T, w/ SRS When calliing ATC, the ATC will respond on any/all channels, For example, at Mozdok, no matter what channel I've selected or radios using SRS, when calling ATC for startup, ATC will respond. How do I force that the radio must be tuned to the correct freq, in this case 137.00, for ATC, or if not tuned to correct freq, no response from ATC? I've set up SRS and Viacom as per the Viacom manual (page 25). Any help please?

Yes, I did! :chef: This is what I was looking to accomplish: local log_file = nil function LuaExportStart() log_file = io.open("C:/Users/George/Documents/Web Page Projects/rising-thunder-alpha-test/data/dcs-time.txt", "w") end function LuaExportBeforeNextFrame() end function LuaExportAfterNextFrame() end function LuaExportActivityNextEvent(t) local tNext = t local TIME = LoGetModelTime() log_file:write(string.format("Time: %.0f \n",TIME)) tNext = tNext + 6 return tNext end function LuaExportStop() log_file:write(string.format("EXIT")) if log_file then log_file:close() log_file = nil end end Here is a link to a "static" working example on github (it's static as the "time-data.txt" file is not being actively written onto on github). But it demonstrates what I am attempting to accomplish.

This DCS World State of Mind is a follow on of my annual short shopping lists which I've done each year, however, with a new name and some new thoughts. With that said, I'd like to give what is called the famous (or infamous) "the good, the bad, & the ugly" approach on my DCS Customer State of Mind. “The Good” In short, in my opinion, Mr. Nick Grey and the TEAM, have created an exceptional living digital museum of historic military aircraft which is not only a commercial venture, but is an invaluable public service. No other software or product concept strives to digitally recreate and to digitally preserve these historically invaluable and rare military aircraft and equipment to the authentic, exacting physical details and duplication of functioning operations such as DCS World. This is simply an invaluable world wide community service, that cannot be overstated, nor should ever be allowed to degenerate, for the generations to come. Not all of us peoples of this World will have the opportunity to go to Duxford, or some other similar event in order to see these magnificent machines running and living in person. And only a very few of us will ever have the opportunity to actually sit in the cockpit of one these machines, and only the most very fewest of us will ever know what it is really like to startup, taxi and operationally fly one of these magnificent beast in the reality of all the detail, skill, and knowledge it takes to do so. However, with the greatest thanks to Mr. Nick Grey and the Eagle Dynamics Team, we, that is, most peoples of this World, who could never dream of sitting in the cockpit of a P-47, and to know what it is like to start-up a Pratt & Whitney R-2800 radial engine, producing 2,000 hp, do have the feasibility to have a significant part of that experience, even from our own homes, as much as technology will allow for us to do so. This is surly a magnificent world wide service that should never be undervalued. “The Bad” In short, incomplete modules. Enough has been said on these forms already about the subject, so as to not rub salt into the wound, I believe the TEAM is aware of this issue, and it is the whole heart-ed desire of the TEAM to address the issue. Enough said. “The Ugly” As an ordinary DCS Word VR customers observation, or maybe more accurately, as a personal perception, for DCS to continue being a "valued commercial product", I believe a Vulkan implementation is imperative, and that it must be “the top priority” to have a Vulkan api implemented into DCS World by the Eagle Dynamics Team as quickly as possible. My reasoning is this, for my system (see sig), while DCS World will perform acceptably enough (2.5.5, that is) minimally, DCS World simply does not perform well enough for me, on my system in VR to justify the continuation of the spending of my available discretionary funds on additional modules at this time, as it is. Now, any reader of this post could very reasonably say your system is not the most up-to date system, and maybe you should think of upgrading your hardware, and that would be a reasonably correct statement. However, while I'm not opposed to building a new system, and I actually do have the discretionary funding available now, even in these times, to build a new "up-to date system" with the "latest hardware" (and it'd give me something to do, should I’d be quarantined). It is more of an issue of not receiving enough personal value return of the experience from DCS World, to the cost ratio of building a new system, that is acceptable for me. What I mean is this, even if I did build a new "the very latest consumer grade hardware" system, I still would not get an acceptable (for me) experience level of DCS World performance wise (fps/stutter) to justify the cost of building a new system, just for the sake of the single application, DCS World. So with all that stated, to follow on with the top 12 items I’d like to spend my hard earned and deviously hid from the Mrs., disposable, discretionary DCS World funds on this year, in the order of, are; A new PC build when/if the next gen of GPU’s (Nvidia, or AMD) are available (and see “the ugly above). I’ll rely heavily on input from the DCS World community for my build planning. The Valve Index VR system. Time to replace my trusty and still working, it just will not die, CH Products HOTAS system with something much more modern and flashy like a new Virpil HOTAS System. VPC MongoosT-50CM2 Grip (w/ dust cover). VPC MongoosT-50CM2 Base. VPC Flightstick Extension. VPC Desk Mount V3 – L (for stick), and V3 – S (for throttle). VPC MongoosT-50CM2 Throttle (w/ dust cover). VPC ACE-2 Rudder Pedals. DCS: Yak-52 (only if it is released out of Early Access!). DCS: I-16 (only if it is released out of Early Access!). DCS: Fw 190 A-8 (however, see “the Ugly” commentary above). DCS: AJS-37 Viggen (only if it is released out of Early Access!). Keep in mind this is only my wish list with likely very little to no real world affluence on the modules that will be released this year or in the years to come. So, with that in mind, please, please, please, keep this as a enjoyable discussion on the modules or products you would like to purchase for whatever reason you want, and please, please, please, not any, "I don't want you to purchase what modules you want because then ED will not have the capability to give me the module that I want to purchase, because my module is better than yours for xx reason and yours is a waste of resources, waa waa, waa...", type post. (just trying to head it off before it happens!) (You should see my long list…) here’s my 2019 short shopping list here’s my 2018 short shopping list here's my 2017 short shopping list DE's DCS World Hangar Modules/Maps Campaigns DCS Eco System Products/Apps Ka-50 "Black Shark 2" (*2015) Su-27 The Ultimate Argument (*2016) VoiceAttack (*2016) P-51D Mustang (*2015) Black Shark 2 Republic (*2017) Vaicom Pro (*2018') Fw 190 D-9 Dora (*2015) F-15C 16-2 Red Flag (*2017) Simple Radio Standalone (*2020) Nevada Test and Training Range (*2016) F-15C The Georgian War (*2017) Bf 109 K-4 Kurfürst (*2016) F-5E Aggressors Basic Fighter Maneuvers (*2017) L-39 Albatros (*2016) F-5E Aggressors Air Combat Maneuvers (*2017) MiG-15bis (*2016) P-51D High Stakes (*2017) F-86F Sabre (*2016) Spitfire LF Mk. IX Operation Epsom (*2017) Flaming Cliffs 3 (*2016) The Museum Relic (*2017) MiG-21bis (*2016) Combined Arms (*2016) Spitfire LF Mk. IX(*2017) F-5E Tiger II(*2017) Normandy 1944 (*2017) WWII Assets Pack (*2017) A-10C Warthog (*2019) (* denotes year purchased) These products are deferred from my previous lists; DCS de Havilland Mosquito FB Mk.VI (unknown release date, however it would be some nice wood to firm up the lineup). DCS Me-262 (still high on my list, even though it’s being delayed, again. Kind of a historical irony, huh? A jet in a World of Props). DCS: P-47D-30 Thunderbolt...(the A-10 of World War 2! Nobody said it'd be easy!). Belsimtech's UH-1H… (deferred to my 2021 list, and only after full multi-crew is implemented, hint, hint, hint, hint, hint...)(Each year I'm gonna add another hint in). DCS: MiG-19P by RAZBAM Simulations… (and speaking of The Cold) DCS: Mi-24P Hind… (A Red Dawn is coming, eventually). DCS: The Channel map. DCS: F-14 by Heatblur Simulations…(OK, Heatblur has sold me on this package with Cobra847’s amazing development updates)!! Belsimtech's Mi-8MTV2 Magnificent Eight...(Deferred to my 2021 list, and only after full multi-crew is implemented, hint, hint, hint, hint, hint )(Each year I'm gonna add another hint in). Magnitude 3 LLC's: F4U-1 Corsair... (Deferred to my 2021 list, however, it’s still on probation depending the quality of their ongoing Mig-21 support). DCS: CVN-71 Nimitz Module... (Deferred to my 2021 list, got to have something for the Corsair to operate off of )(I'm not sure which studio is actually developing this module, or if it’s still planned at all). These products have been depreciated; Magnitude 3 LLC's: Junkers Ju87 D-5/G-2... (depreciated, as in project canceled, really sad, as this thing would have been a scream while doing it's thing). Polychop's Horton Ho 229...(depreciated, as in project canceled, sad, it would have been sly to finally have a stealthy aircraft. Do hope another studio picks it up). Magnitude 3 LLC's: Iwo Jima Map...(depreciated, as in project canceled as far as I know).

My 2019 DCS World Christmas Wish List!! It’s time for what will be my third annual DCS World Christmas Wish List! All of these 12 Wishes (a "Twelvetide") posted here are not on any "in progress" list, or "planned" list as far as I know, but are just that, a Christmas Wish list. And also, while some wishes are carried over from last year, some are new, and some are higher, or lower on the list. There is so much being added and proposed for DCS by Santa’s Eagle Dynamics Workshop Division now, it's becoming a little more difficult to come up with wishes which are not already in the works, or planned. Even-so, I’m gonna give it a try. Now, for my 2019 DCS World Christmas Wish List, in order... For sure, this is not an original wish, but one that is becoming really needed more and more so in the World of DCS, and that is a couple of modernish, or 1980'ish full fidelity Russian aircraft, My wish is we could get the famous DCS: Su-25T as a full fidelity module, and at least the World famous MiG-29A as a DCS full fidelity module! I mean, the Russians are just being left out in the cold, and really under represented in the World famous World of DCS. Wishing Santa will fix this! Again this year, high on my DCS Wish List is a "Pro-Track Player/Video Recorder" module which has complete upgraded functionality such as reverse play, typical and expanded camera lens features, programmable track "key-frame markers" for camera positional movements, pan, zoom, focus functions, and etc, etc.., for easily capturing good camera shots and video effects of our missions, for the production of professional quality videos. Neither is this an original wish by me, however, I think it really deserves being brought up to Santa, and that is for the multi-crew training aircraft, for example the L-39, Yak-52, Christian Eagle, C-101, and etc. to have the instructors position as a free module, but only usable freely in coop with a client who has purchased the module. In this manner, a DCS client who has taken the initiative to purchase the module has the ability to request personalized instructions from a buddy or other client who may not have the module, or just give demo, or joy rides to friends or family in VR who may not be interested in learning to virtually fly, but who would enjoy the occasional virtual joy ride (DCS does has some beautiful scenery now!). Still needed, An updated, very comprehensive, in-dept manual for the DCS World Mission Editor, especially an extensive systematic explanation of all triggers, functions and flag operations, along with numerous examples of how to use triggers, functions, and flags from simple to complex solutions for the mission editor. Another carry over from last year, however, still greatly desired, for "Yo-Yo" to write and publish his memoirs, or some such as, "Fundamentals and Theories: Comprehensive Aeronautical Engine & Flight Mathematics and Dynamics as Applied to Simulations". Wheel chocks for all the aircraft modules, and for the aircraft to be chocked at initialization of a “cold start” mission. This is like, aviation 101... A "Pro-DCS Model Viewer" for us home cockpit builders, which would give us the dimensional, articulation arguments, and textural data necessary, and the capability to export this data into a suitable "Fusion 360" file format, allowing us DCS World Cockpit builders to have the ability to design and fabricate an accurate, high quality, home cockpit using the materials and processes which work best for each individuals circumstances. A better, easier, and shall we say, a more "sanctioned" process than what is possible now. A DCS B-17 Flying Fortresses Multi-Crewed/Player Module (this would be the Ultimate DCS World Babe, I'd hang posters of her on my garage walls, nose art and all, don't care what the misses says. As I understand it this aircraft has been depreciated by the third party developer who initially proposed it, however, I’m wishing another developer, or the Eagle Dynamics Warbirds Team will pick it up, and that is the Junkers Ju-87 series of aircraft. These things would be an absolute scream in VR! A C-47/DC-3 Multi-Crew/Player Module (pilot, co-pilot, navigator, radio operator positions), with cargo’s of various types, troops, paratroops, VIP’s, passengers & etc.., and animations of loading/embarking, unloading/disembarking, and cargo and paratroop drops. A Ju-88, bomber variant, Multi-Crew/Player Module, all positions! To kinda even out the line up. Virtual “Room Scale Locomotion” in the Word of DCS, especially at the airfields. The ability to set up a couple chairs in my garage, and just sit and watch a virtual airshow being performed by the world famous VFAT, with a friend or two, or more on a multiplayer server, and also being able to get up, and do a walk around of the aircraft and other equipment being displayed at the virtual airshow. And as a note from my past Christmas Wish Lists, a few wishes which have been tentatively promised, as I understand it, anyway. More realistically (as much as possible anyway) modeled RF (radio frequency) environment, with more realistic procedures for us human and bot (AI) entities to communicate/interact with each other. Animated ground crews, at least for the carriers first, and then, as I understand it, animated ground crews are planned for the land based operations at a later date, at least part of my 2018 No. 4 wish. Virtual crew ready rooms, at least for the carriers anyway, again at least part of my 2018 No. 10 Wish! So after reading my wishes, if you'd like to ring in on the wishes you'd like to see under your DCS World Christmas tree this year, ur, well ok, maybe Christmas 2020, or 2021, please do so! However, please, keep this as a fun and enjoyable discussion on the wishes you'd want under your DCS Christmas tree for whatever reason you want, and please, not any, "I don't want you to get the wish you want because then Santa Clause's elves will not have the capability to give me the wishes that I want, because my wish is better than yours for xx reason and yours is a waste of Santa's resources, waa waa, waa...", type of post. Beside, that'd put you on Santa's bad boy list, and none of us would get your wish then... Wishing the Eagle Dynamics Team, fans, customers and supporters a Very Merry Christmas!! (My 2018 Christmas Wish list is here...) (My 2017 Christmas Wish list is here...) (and lastly, the disclaimer...) I'm only doing this for the Christmas Spirit & enjoyment of it all, and to record a few of my insane DCS World wishes which have been rattling around in my Crystal Ball this year, again. I understand that any wishes posted 8 days before Christmas are not likely to happen this Christmas. Not, unless Santa Clause were to release his entire elves workshop to Eagle Dynamics this month, and that's not happening, but these wishes could make for a great 2020, or 2021 Christmas present!