Leaderboard

T-90M MBT 1.0.0 released! Changelog Version 1.0.0 Release version

Good Morning/Good Afternoon to you all. I hope everyone is doing well. I have released USS Oak Hill LSD-51 version 1.0.2 Page one of forum #7. Thanks to Marroux for creating the ship's information file located in the Encyclopedia folder for all the ship mods. One known issue that Marroux brought up is there may be some FPS drop while taking off from the Flightdeck as a player. He found that it was related to the LODS file. This is something we will have to research to find out why the LODS file cause FPS to drop. If someone knows how to get each ship to display the livery name of the ship. PM me! Otherwise, all the ships from the livery will display the name of the USS Oak Hill. PM me if there are any major technical issues. Thanks and Enjoy the Updated AI Ship Mod USS Oak Hill LSD-51.

Thanks guys! The thing is... making these assets is me doing fun stuff instead of daytime work. So for me, making these is equivalent to taking a rest.

I sort of think this was talked about one time before, what would happen if it all fell apart, the short answer was your stuff would be fine in that you would still be able to access it. Or we would do our very best to make sure that was the case. That said we are very very healthy right now and continuing to grow and get stronger, while nothing is for sure in this crazy world, this should not be one of those things taking up any brain power to worry about.

Alright, it's pretty much concluded. Too many changes to list. From the top of my head... pretty much all textures were redone (again, argh!) with readjusted colors, and better matching. The old 2.5 airport terrain textures are back (much nicer) restored and matched, and hangar covers matching the terrain. Some adjustments in the trees, nicely matching the terrain for each season, and including barks and normals from "Taz Better Trees" (better definition and optimization). And there are all new ShadingOptions (not just gamma values changes) for the Caucasus map, which complement all changes very nicely. Currently testing the "LOW" terrain textures (lower resolution/detail version), always included with the mod and meant for those of you unable to run them at "HIGH". These are not "half sized batch converted", each single one is downsized and sharpened a little, to keep detail (quite the task). Below are two quick screenshots taken while testing the "LOW" terrain textures, Summer season set at 10.30 AM, near Tsatskhvi:

T-90M MBT 1.0.1 released! Changelog Version 1.0.1 Fixed missing track textures Thanks, but they can also be green.

I have no idea why people pay for a preorder, then get all angry when the thing that never had a release date, where they explicitly state it won't have a release date, doesn't have a release date. It's out when it's out. Note to your future selves: Don't pay for a preorder, just go back to the game, play, chill, forget about everything that isn't already out. Enjoy what you have. You're not suited to preordering, so don't do it. It's fine, completely understandable. Preordering niche products isn't like preordering from AAA developers (which is crazy stupid, but that's another discussion). We only preorder to support the niche products. No other reason really. We otherwise gain absolutely nothing, except *maybe* a few dollars off the price. There is no advantage for the impatient to preorder. For those who've been playing this genre for decades, we've seen it before, and we're just happy to have the chance to see such amazing products in our lifetime. Maybe you haven't got that perspective yet, but I grew up in the time when the horizon was just a line on the screen, 48kb of RAM was what you had, and that was the terrain, full stop. If you're vulnerable to all the hype, create a bit of space for yourself so you don't get worked up about this, it's trivial.

More drama than a Jane Austin movie! ... It'll get here when it's ready, tested tested and tested some more. Use this and waiting for other DCS modules, to learn about patience, seemingly a lost art these days.

It's the T-90M.

Northrop YF-23 Black Widow A Cad Nav model. Saved games install. FC3 flyable. F-15 FM and cockpit. Skin template included. OvGME ready. Weapon load out, and other code corrections and changes, Spino! I thank you for the great job! All 3d work and extra skins are my own, Yea, sorry bout that! Enjoy! https://www.dropbox.com/s/e2ruymp6xiue4mb/YF-23 Black Widow II V3.8.0 R.zip?dl=0 Please report bugs via PM . All screens, Post here! And liveries gladly accepted and will be included in the next release. Have fun!

Thank you! There are two main reasons making my assets more resource intensive than DCS core assets. 1) Polygon count. My assets are a lot heavier in general, a lot more polygons for DCS to keep track of. This could be improved by making lighter assets for when zoomed out (level of detail - LOD). I could also optimize my meshes to reduce polys. Unfortunately, both these options take more time, which I rather spend on new assets. 2) Textures. My assets run pretty heavy 4K textures, and a lot of them. I could reduce texture sizes for smaller parts of the assets to make them less texture heavy. I could also have fewer textures (less detail per texture). But I kind of like the nice textures so I'll probably keep them pretty heavy. Lately I have been optimizing them a bit by using different texture resolution depending on the size of the object they are used for. This makes a lot of difference both in loading and in actual storage space. So, for you guys out there running very low spec, I'm sorry, but it is what it is. I'm a one man operation. Fortunately the MT version seem to (at least for me) improve these issues a lot. For reference, I run both development and DCS in 2160p on a 13700K with 64 GB and a RTX 3080.

So sad that mil-sim like DCS is getting so low priorities on very important problems like this one. DCS - one of best sims of its kind in the world, with best simulated combat aircrafts, is nowdays still based on just 20 years old simple core (one human generation, cars went to electric propulsion, PC are 10000x more powerful,...), where CHAFF and FLARES are just lottery game, FLAREs only big or small - nothing between, affected only by sun but nothing else from nature environment... That just sad. to have nice polished aircrafts, but behind that shiny mirror we have just guess game - so nicely shown, how ED treats InfraRed world in DCS, just on base of pictures and user reports, not on base of real physics and calculations.

I would love to see an M1A2c / M1A2 Sep v3 (there is now a Sep v4 but there aren't as many details on it as the v3) as a counter to this. With Trophy APS, ARAT ERA, M829A4, M1147, and the remote control .50 cal. Either way I love to see some new MBT's. - Gundamator

Diskussionen über ein bestimmtes Modul bitte in einem separaten Thread und respektvoll. Und denkt bitte an diese Community-Regel: 1.2 Die Mitglieder des Forums müssen sich gegenseitig mit Respekt und Toleranz behandeln. 1.5 Alle Off-Topic-Beiträge werden ohne Vorankündigung gelöscht. Beiträge sollten zum Thema des Thementitels passen und Themen sollten zum Thema des Forums gehören, in dem sie gepostet werden. Beiträge, die versuchen, das Thema zu kapern, zu trollen oder Fragen zu stellen, die bereits beantwortet worden sind, werden ebenfalls als OT betrachtet und gelöscht. Bei Wiederholungstätern können Verwarnungen ausgesprochen werden.

Glad you like them! I didn't know about the OvGME Repository feature. I'll definitely look into it as I like OvGME. As mentioned before, look into the High Digit SAM mod. Nice! Thanks for the suggestions and inspiration.

You work fast! Regarding the T-90's usage in the ongoing Ukrainian war, might you consider adding cage armor to the roofs of the T-90M in a future update? In the meantime, I will work on liveries with Z, Z with a square around it, V, and O painted onto the T-90, and other Russian vehicles like the Pantsir, Tor M2, and 2S38 Derivatsiya PVO. Also, for those who may not necessarily know, liveries won't work unless you enter this line of code in entry.lua mount_vfs_liveries_path (current_mod_path.."/Liveries")

At night you have to turn on the lights to launch instead of a salute.

Please ED, remove unnecessary liveries from DCS builds, put them in separate packs, for optional download. MiG-21 livery folder alone takes 6GB, Christen Eagle's takes ~4GB... all in all, it's like 20GB of unnecessary liveries that I have to remove every time a new OB update comes around (due to limited space in SSD). Since the last big update, I'm forced to migrate the DCS folder to my HDD, update there, remove unnecessary liveries and then migrate back to SSD... it's no fun. I think it would be better for everybody to keep non-essential liveries as separate packs (faster downloads, less stress on the servers, fewer complaints from me...:lol:).

BORT NUMBERS FIXED 2023 https://www.digitalcombatsimulator.com/en/files/3316791/

Hi, I’ve searched long for Approach, Arrivals or Departure-Charts for Ramat David but didn’t find anything which was complete. So I created my own Charts. They are 100% fictional. I have no official information’s or insight in this airports procedures. Therefore it should be clear, that the charts are for sim use only. All headings are magnetic north with 5° variation. According to this the effective date is the first Jan 2020 in DCS. As template I used the style of jeppesen charts to create my own. It is a large effort to create and check all headings, obstacles, altitudes etc, so I don’t pretend they are 100% accurate. https://www.digitalcombatsimulator.com/en/files/3330785/ In the pack is included: High resolution charts · STAR o 10-2A Ramat David STAR BARZI o 10-2B Ramat David STAR GALIM o 10-2C Ramat David STAR MOCEV · SID o 10-3A Ramat David SID BARZI o 10-3B Ramat David SID GALIM o 10-3C Ramat David SID MOCEV · Ground Chart o 10-9 Ramat David Ground · Approach o 11-1 Ramat David APCH RWY33 o 13-1 Ramat David APCH RWY15 o 13-2 Ramat David APCH RWY09 o 13-3 Ramat David APCH RWY27 o 19-1 Ramat David APCH RWY29 o 19-2 Ramat David APCH RWY11 Downscaled Charts for DCS KNEEBOARD Day Downscaled Charts for DCS KNEEBOARD Night

Hey Guys! I have released USS Oak Hill LSD-51 ver 1.0.3. If the mod appears ok for you DCS. Then you don't have to download the latest update. Changes Made: --Removed the MASS Electronic Countermeasures from the mod's main Lua file which may cause the ship not to appear in DCS. --Removed extra textures in 3ds Max. Thanks for letting me know Eddie. I intended to remove it before release but forgot about it. Thanks again!

В DCS отсутствует класс MPAP Украина Россия

When launching from the catapult on the carrier, the player's pilot now has the salute animation the AI have been using.

Haha, the god damn tracks again. I’ll fix it.

Wonderful, thanks. Issue replicated and reported.

Fantastic work ! Thanks Currenthiil !

This modification freed up 1.4 gigabytes of video memory. 8.2 is used instead of 9.6. Why is optimization done by an ordinary user and not by the ED development team...? Respect to the author of the mod for his work!

@Thinder my role here is not to moderate discussions but I would appreciate if you were more polite when addressing @Bremspropeller. @Istar_Eldritch from what you describe, the problem seems to be that vJoy is tripping the automatic FFB stick detection. I have no experience with this software but, if it has an option menu, can you check if there is an option related to FFB? Otherwise, if you don't want to uninstall the software, in the DCS MISC. Option menu, try unchecking the Force Feedback checkbox. If it still doesn't work correctly, please report back and we will see if there's something we can do about it.

It is the task queue. The FAC task needs to be completed before the options are set. So move the options to the top. https://wiki.hoggitworld.com/view/DCS_editor_FAQ#Why_isn.27t_an_AI_task.2C_option.2C_or_command_working.3F

We will release any new feature and update only when it's ready for customer consumption. That's all I have for you on this.

https://www.digitalcombatsimulator.com/en/files/3328824/ BORT NUMBERS FIXED

I think Reflected mentioned that in the eleventh hour, ED changed the Normandy map frequencies. Not sure why they would do that...but now Reflected needs to update the freqs. I would imagine it's a PIA...LOL.

Only ED can answer this topic. I would hope however that if this ever did unfortunately ever occur, that ED would release some sort of last build or similar that turned off the licensing check to just allow people to install and play bypassing the registration checks, but that’s hope, no guarantee. The simple fact is, when you buy licensed software that requires activation, you never truly owned the software or have rights to it. There is always a risk, whether Adobe Photoshop or now even Microsoft Windows considering calls home periodicly to check whether or not you’re operating system should still be activated all these have the potential to disappear on us. Or even be “turned off “if they deem the region, we living or our conduct is no longer within their terms and conditions.

Of course both

General suggestion to ED: DCS should log a warning when scripts cause very poor performance. Not every time it happens as it could happen every frame, but once every 5 seconds or so when the same script offends more than one time. More than one because external system stutter could randomly catch any script perhaps, but twice on the same script is likely no longer a coincidence. I just solved my stuttering issues which were giving me 1% and .1% lows of 16/17fps on an MP server with a 90 fps average; and even free flight SP was giving me maybe 110 fps average, but 30-40fps on 1% and .1% lows. The stutters were happening both every 2/3rds of a second, and bigger ones once every 2 seconds or so consistently. My solution was disabling DCS-Export and DCS-BIOS. I dove deep into profiling DCS on my system while trying many of the common suggestions and nothing had any impact on performance. I spent a couple of days on the task so some advice: Use MSI Afterburner (you probably already are if you know you have microstutters) so you can actually see what changes matter and which dont Test the same map, mission (or one MP one SP) with the same module. Different DCS modules have different baseline performance even if they're sitting on the same airfield I only delete the fxo/metashaders folders if graphics drivers or options (in game or driver/DirectX control panel) are changed; spare yourself the shader compile time. Most of those dealing with this have end systems we know should average 60fps+ on quite high settings. Despite this, set your graphics options to low, minimally texture quality visible range, and preload radius, and verify if you still have the stutters. If you do, set your graphics options back to what they should be because that isn't your problem. RAM speed isn't going to eliminate stuttering assuming the dips are super super low, well below what you know your system usually does. I have PC32000 DDR4 RAM (not the fastest), turning XMP profile off/on made a substantial difference but given this is a 2x speed swing and it didn't half my 1% and .1% lows, it shouldn't have been my focus. My 1% and .1% lows went from 17-ish to 12 on an MP server. With 5950X and 64GB of RAM, no background service or other running program made a difference. Even ones that I personally can see take up a little too much (ElGato Audio Service or something). I could have many Chrome tabs open, many with YouTube, and even playing a YouTube video during gameplay. This made no difference. DCS full repair, with removing extra files found did nothing Disabling hot pluggable devices in DCS did nothing for me Disabling Microsoft Root Device Enumerator (and a reboot) did nothing Disabling fTPM in UEFI (Trusted Platform Module 2.0) did nothing for me Closing nVidia GeForce experience had no effect The problem persisted across multiple nVidia driver versions Setting a higher PBO max boost didn't help things I tried various combinations of G-sync, V-sync=game setting / fast. Though I knew the issue wasn't graphics, frame presentation/sync still changes game loop behavior I dove deep into profiling with: Process Explorer, Performance Monitor, uProf (AMD specific). I noticed page fault and presumed that maybe I was dealing with unecessary disk access (my RAM is fast enough, even an nVME SSD could cause hitches). This was not my problem DCS was showing me page faults happening in a sort of spiky way but reporting on page faults / hard faults are generally every second so it's impossible to line it up with the fluid frametime graphs within DCS or MSI Afterburner uProf is a non-trivial tool to use, and was showing me a miss rate on L2 cache that I thought was somewhat validating my suspicions. 5950x has an L3 cache though but I couldn't get uProf to profile L3 cache hits/misses (likely a bug with the tool right now). Arbitrarily, I considered maybe the DCS log might be a culprit of something were being logged (disk writes) excessively eventually forcing a very slow IO sync so I opened up the log to see what was going on during actual simulation. I noticed a frequent (but not excessive) message about a DCS-BIOS script failing to compute or construct the F-16 DED line right (this was my test scenario) First step I took was to update it in case there was a performance problem. That didn't fix it Next step: now I'm reminded that I have a bunch of DCS scripts that could be the culprit so I disable them Plugins that caused no performance hit in terms of the stutter: SRS, Tacview, SimShaker, VPC Link Tool (vpcGameGUI.lua), DCS ScratchPad Problems: DCS-BIOS, DCS-Export Again, each of those plugins created massive microstuttering down in an unacceptable way. Everything I tried that didn't work, I have turned back on and I get no stutters, great performance. They also lowered my average FPS noticeably too, but I would be totally fine with that cost given how I use them with my StreamDeck and I'm well above 60fps anyways. Removing both plugins my .1% lows went up to 73 from 17 in MP, and from 35 -> 85 in the SP free flight Syria mission. My 1% lows are even higher, and sometimes surprisingly close to my average frame rate. So now I have to overhaul my StreamDeck profiles to operate through hotkeys instead of the DCS-StreamDeck plugin...bummer.

Good catch.

Well, I was definitely not complaining about the responsiveness of the trim, but about it not working at all. I had a look at my setup, and it seems like the problem was indeed related with one of the connected devices. I was using vJoy to emulate the toe brakes on my VKB T-Rudder pedals. Removing vJoy and using the pedals directly solved the issue. I have a hunch that vJoy emulates something related with force feedback so that is probably the cause. Its a bit strange, I would definitely not expect the pedals to affect the pitch and roll trim but that was definitely the case. Do you know if this would be solved at some point or if I can configure it somehow so I can still use vJoy? Feel free to close thread if it becomes problematic @fausete

Hi, There's a current issue (introduced in the last patch) with the yaw damper sometimes amplifying yaw motion instead of dampening it. This has been solved internally. Regarding the general FM feeling, strength of adverse yaw, stability... Our SMEs (which have thousands of hours flying the F1) have tested it extensively and verified it is an accurate representation of the real aircraft. As always, reports of specific issues are appreciated but it's always much more effective if they come with a track or a video showing the issue and, in cases like what is being discussed, some evidence backing the claims being made.

On the offchance anybody is interested, my flight was today. Lot of fun, very noisy. Radio wasn't plugged in, so we couldn't communicate (unfortunately costing me an opportunity to take the controls) but was a great day. It was way louder than I expected, very glad for the headphones. Erik Johnston was there so it is likely the takeoff and landing was recorded. -edit Cockpit upload It's a bit cramped in there so I had trouble taking photos properly -edit update for history This plane was built in Grand Prairie, TX in 1943, was based at Avenger Field and utilised by WASP among others, at least some of whom went on to fly/ride in the plane again in modern times 60-70 years later. So it's a proper ''active duty WWII plane'' although it was not deployed overseas, being a trainer.

What is the point of this huge wall of text both explaining the obvious and somehow also begging? Do you think it's sitting on a shelf somewhere and Nick Grey is like ''NO NO, not yet... let them... stew in their angst a bit longer. The suffering makes the meat taste... sweet.''? They will release it if/when it's ready, and forum users writing lengthy discourses on the ''community's needs'' and ''ED responsibilities'' is, at best pointless.

12. / JG.54 Interesting fact about this JG is, that 12. Staffel bore light blue waistbands according to newly surfaced pictures. Several of the other JG´s didn´t so one good reason to include this.

while I'm making a model. there are programmers, but it is difficult for me to communicate with them with a translator. Немного свежего ракурса

FB.VI entered service in May 1943. Initially with Merlin 23, but with Merlin 25 after the first few hundred produced (out of over 4000). The Merlin 25 was at the time the best Sea-level version, and was considered a big boost to performance. In comparative tests it was faster than any Spitfire version including the low-altitude hotrod Griffon powered Spit XII. Until mid/late 1944 FB.VI intruders felt comfortable that they can out-run the contemporary 109 and 190 variants. This of course may suffer from survivors bias, as those that were able to out run the enemy came back to report it. Around may/june 1944 they requested the use of 150 octane fuel and +25 boost for day operations, since they felt they no longer had the speed advantage. This is the time of the 109G14 and 190A8 I suppose. Our mosquito is limited to +18 boost. In addition, there is some ambiguity regarding what was the sea-level speed of “our” version of the FB.VI. Within that range, our FB.VI is at the slowest end. It matches the performance tests of HJ796 which was shown to be underperforming. There is no official test of FB.VI in our exact configuration that is not HJ796, so some extrapolation is required from other tests (e.g. HX809). These give a sea-level speed estimate that is 15 mph faster than the DCS FB.VI, which is quite significant, though not entirely game breaking. Real planes did have variance between individual air frames - we got a lemon one…

Stugna-P ATGM 1.0.0 released! Changelog Version 1.0.0 Release version

I would add to @cailean_556's comment that precision attack mode should include attacking ANY static object.

Still being worked on. Progress is going well. I would expect releasing it before the summer.

I think the solution would be a launcher like other games have, where you can change settings, install/remove modules, mod manager (repository support), livery manager, updater/repair etc. I have diskspace (for the time being), but I do understand people who doesn't. So I support the request!

Yeah, IR seeker in DCS IGNORES FLARES before missile is launched. Above mentioned BUG proved to be an issue to all IR missiles. IR_seeker_IGNORE_FLARES_BUG.trk