DirtyFret

Hey Razor, Those are very good questions but unfortunately I don't have answers for them , only guesses :). I noted the same discrepancy in naming convention and I just assumed and deduced that since the original .lua file has on the GAU_AP ammo "cartridge_mass=0.083" that this value cannot be the real physical weight of the whole cartridge. The lines "mass" and "round_mass" I assumed to respectively be "projectile mass " and "cartridge mass" because the values closely represented real life values. I have tried to figure out the method with which DCS computes AP damage but I do believe that "v0" and "mass" values play a part on those calculations in conjunction with "AP_cap_caliber". I haven't figured what that "cartridge_mass" value stands for or what its use is. The "cartridge_mass=0.360" is from the original .lua and I haven't altered it at all. It could have some role in explosive damage calculations because that value matches the "explosive" (mass) value. The Da0 is a somewhat mystery to me. Even though, I (and many others) know by testing that by decreasing it you reduce the spread and by enlarging it the spread increases. I don't believe it to be of any real physical value(e.g. milrads). I believe it could be just a coefficient in the bullet spread/spawn calculations inside DCS game engine. I must admit though that I am a total amateur in this matter and that "MOA" measurement you refer to is unknown to me :). Hope my guesses answered some of your questions Razor, if you do happen to stumble on some info or revelation by testing or otherwise please do share :thumbup::) Regards D-F

May I suggest you try and re-downloading a pack from the #1 post and try using that. If the radio dial issue still persists with the re-downloaded pack would you be so kind and post a screenie?

Sry for the absence/silence. I am glad to see that this mod is still being used. I put a lot of effort into it. :thumbup: Happy to hear that you like it. Maybe one day, but with my current work schedule and other commitments I cannot see that happening any time soon. Please try downloading a full pack and see if the radio dials are working. What DCS version are you using? That patch/hotfix 1.1 is obsolete. What DCS version are you using and what color scheme does this? May I also ask which radio dials? It is probably an alpha channel issue. I just did a super quick fly around in night and with panel lights and could not see any glaring issues in 1.5.5. Did you try downloading a full pack or did you use a patch also? Try downloading and using the 7z free open source program. Happy flying, and i'll try to fix any issues as soon as I am able to.

File updated , working in 1.5.5. OB (steam) Please let me know of any issues and I'll try to fix them a bit faster this time :music_whistling:

Sorry it took ages :noexpression: I have had an extremely busy real life schedule. Links updated. Mods working in 1.5.5 OB (steam). Let me know if issues persists, I'll try to be more quick with fixing them this time ;) Notes: The GAU data has been updated with the info from OrbitalATK datasheet

Thanks for this. Happy to have been a (small) part of this project. :thumbup:

It's the fact that the TAD map is comprised of a few hundred separate tiles with a pure 1:1 square map geometry (1000x1000pix). To get the f10 map to work you would have to compile the 1:5m , 1:2m 1:500k and 1:250k (something like Linos map) res maps from the F10 map and then do a georeferencing on them using the old tiles as reference afterwhich you cut the new tiles from the newly compiled map files. Or at least i think so. There might be a easier or a quicker way but i just havent figured it out:)

Hi Braeden. Yes it is possible. Although according to my estimation it requires several steps, a few programs and about 6-12months of time if done alone. :) PM me if you want my suggestion for a workflow. If you however want a quick improvement try the excellent TAD Map upgrade. The author of that pack and I are currently on expanding the TAD map on the 1:250k level. Just my 2cents D-Fred

Thx for letting me know. I'll start troubleshooting it asap.

Thank you. :thumbup:

Try creating a overhead markpoint and then doing a offset on that. Press MK on the CDU panel as soon as you hear the call (creates a overhead markpoint) -> AAP page select to OTHER -> press OSET FSK -> Enter the Markpoint letter into the scratchpad for the overhead markpoint and into L3 -> enter MH/DIS onto R5 -> press R6 to create the offset waypoint. Let me know if it works.

ah, ok. Sry for double posting then, but I feel this blog deserves all the attention it can get. Maybe a moderator will merge these threads or something.

Very interesting read. Lots of info on basics and some advanced stuff like ECM and RADAR functionality. Very well written articles with references. I highly recommend: Blog P.s. blog is Not written by me, I have no affiliation with it except reading

Okay, I have spent the couple last evenings trying to understand the russian cyrillic alphabet, trying to find a suitable font and trying to build a proper workflow for doing a RUS version of this but to no avail. I tried hand drawing the RUS texts to google translate and then copypasting the digital version to Photoshop in cyrillic font to some success but the workflow was unbearably slow. I mean slow as in "well-see-a-F16-and-AH64-in-DCS-before-this-is-finished"-slow. I have to admit to myself and to you guys that I can not do the RUS version of this alone so I am asking for help: If you are literate in both english and russian and are willing to help me (or know someone who could) send me a PM. Photoshop, willingness to spend some time on this and (some) skills are required. P.S. If someone could help me translate this to russian and point me where to post it in the RUS side I'd be happy also

Hmm, I havent had any issues with SP AAR refueling. As a matter of fact I took it upon my self to improve my skills and remove the fear of AAR. I did around 1-2hrs/week of AAR training for about 3months and now I reached my first milestone: No-disconnects from about 40% full in daytime with good weather. TRACK

Who knows. I have a few projects underway including updating and tuning this one so maybe one day I will find time to start with the Huey cockpit textures. ;)

If i am not mistaken : (L MFCD) Press STAT-> Press NXT -> scroll down to THRTL -> using the CDU or UFCinput a value to the SLEW OSB. Smaller value = faster slew , larger value = slower slew.

Seeing the nice photos from your trip I got super excited. As such, I donated some of my superexcitement to you guys via the PayPal link. Not much, but something I can give. I wish you and your team perseverance and guts on this project. That aircraft is gorgeous

You're welcome Skullleader my friend. Files updated/patched, an R863 number alpha channel mismatch corrected (a remnant of solving the previous issue with those same numerals :music_whistling:) . Please let me know of any issues P.S. Patched file attached (overwrite existing). So you don't have to DL all of them again cockpit_mi-8mtv3_dev3.zip

Indeed DCS 1.5.4 in my case supports SLI only if I force it to AFR2 mode via NVidia Control panel. No-go for SLI if any other mode is selected.

Very sincere and good update. Thanks. Keep up the good work.

As far as I know how to test and measure SLI works and provides a benefit in my case. I use a twin GTX 980 Ti setup. SLI bars green FPS gain of about 30-40%. Is there some other way to test than checking the "green bars"?

I've been thinking about it but I am bit afraid of how the wifey will react. Still remember her reaction to my 4k 48" monitor/TV setup. :megalol: In your experience how is the resolution with the head gear? I know the pixel amounts it produces per eye but in your personal view, is it the same or better than with a good (large) HD monitor or 4k? Are there any noticeable differences to reading the gauges or spotting targets? How about motion sickness?

I Can confirm that changing for Steam OB to Steam release version corrected the taxi issue on Mis02 but I am still not getting shot at by the SAM site even if I fly right over it. Did the rest of the mission work correctly for you Foul Ole Ron?

I run latest Steam OB 1.5.4. Reporting my experience with the "taxi-issue". I am able to "fix" the taxiing issue in TEW M02 by switching 1-2's starting spot. However, the rest of the mission does not seem to work properly after this anyway. From what I have seen/read from YT and forums is that a SAM site is supposed to try to shoot you down in M02. No trigger of that kind activates for me. I just fly the ~300mi for 1h:40mins and then land safely with all my wingmen buddies. :pilotfly: