Shadow_1stVFW

Try designating closer to the target, try steeper dives (like 30* just to test) check your winds. Most importantly, make sure your speed isn't super crazy. Like 350-480. Sent from my SAMSUNG-SM-G900A using Tapatalk

Hold onto the file, I'll help you troubleshoot it tomorrow. Sounds like you didn't paste the right thing in there Sent from my SAMSUNG-SM-G900A using Tapatalk

How is that not the point? What information are you missing that you want? Sent from my SAMSUNG-SM-G900A using Tapatalk

Haha. I just pointed you to the thread. I had the same question. If you check out earlier in the thread, one guy put out a file on how to make the numbering system work on any skin. I plan on testing that to make my skins work Sent from my SAMSUNG-SM-G900A using Tapatalk

There are none just on the map. The mission designer needs to place one.duting mission design. Sent from my SAMSUNG-SM-G900A using Tapatalk

In the downloaded skin, find the description.lua add this code and replace the <texname> with the name of the skin. It will disable the dynamic numbering system https://forums.eagle.ru/showthread.php?p=3039840 Sent from my SAMSUNG-SM-G900A using Tapatalk

I had an issue in 2.0 as well. I had been flying for over an hour, I landed and rearmed and refueled, just prior to taking off again, I accidentally pulled the emergency canopy release level and expierenced the same fps loss, though only in the cockpit. Sent from my SAMSUNG-SM-G900A using Tapatalk

I just noticed the D2M mounts are missing textures in 2.0.

Yeah, a status update on this one would be nice. This, to me at least, is a big ticket item Sent from my SAMSUNG-SM-G900A using Tapatalk

Yes, that's what I'm trying to do. I'll check oit it later and get back. Thank you, much. Sent from my SAMSUNG-SM-G900A using Tapatalk

Has D2M been activated in the latest version 2.0 with this newest update? I couldn't get it to activate at all last night. Though if Monkeys post is correct, those are all the units I let shoot at me. Sent from my SAMSUNG-SM-G900A using Tapatalk

Haha. Same experience, same skin, same result. I think we all know the skins need to be modified, we are asking if anyone knows how to modify them to disable the numbering system so we can use the skins we downloaded. I don't mind doing the work, I just want my skins to work Sent from my SAMSUNG-SM-G900A using Tapatalk

I haven't had any issues with it at all. If just check a simple mission with no weather or stores. Sent from my SAMSUNG-SM-G900A using Tapatalk

Known issue. Not yet corrected. Use buttons for now. Sent from my SAMSUNG-SM-G900A using Tapatalk

What's it doing, what is different in the menu, have you tried to repair your install? CaptSmiley is very helpful, but he needs to know as much about the issue as he can. Sounds like something in your install though. Is not a wide spread problem. Try to repair. Sent from my SAMSUNG-SM-G900A using Tapatalk

I, Second that. Sent from my SAMSUNG-SM-G900A using Tapatalk

So the LUA file is here (mine is installed) ...\_MODS\NVG Mod M-2000 - Werewolf\Mods\aircraft\M-2000C\Input\M-2000C\keyboard The file is Default.lua The lines you need are under the -- Cockpit Displays & Illumination section NOTE: they won't be exactly this, I have mine shifted as I already had page up and down assigned. So, what you should do is copy and paste your default.lua into this one. I renamed the mods file and pasted mine here. Then copied those line into my file. What this does is keep your keys. Paste these in there. And delete the renamed file that came with the mod. Then install via JSGME. And you're done. (Keep a clean backup of the mod)

Thanks, that was it. My analysis was incorrect. DCS never restarted until I clicked the vsycn option.

It's ticking the vsync box. Once I click it once the UI gets dim, unticking will not bring the original brightness back

So after actually getting back on my computer again changing the options back to what I had them set too still causes the screen to dim. I renamed the saved games/DCS folder and the screen is fine. I add the options through the in game GUI and it's dim again. I'm going though now to try and figure out what option is causing it. But it still seems bugged.

If it is the mod, what you can do is go into the NVG mod, then find the input file, I forgot it's title but it's pretty simple to find. Open it in notepad++ scroll down to the 3 commands for the NVGS and copy and paste them into the file of the same name in your Mods/M-2000C... folder, then you can either delete this file from the mods (not recommended) or you can save the edited file in the mod, delete the lines from the non modded folder (all they do is add the lines to the control editor) then enable the mod. What you've done is you've copied your current keyboard current keyboard input file and added the new commands for the NVGS. Now they'll be visable for the controls page. Then you've put your current key file into the nvg mod. So when you enable the mod, you'll be enabling the NVGS and you'll still have your keyboard commands as you've assigned them, plus any that might be used for the kneeboard. That's what I've done and it's worked. Sent from my SAMSUNG-SM-G900A using Tapatalk

Talk about customer service! Thanks! Looking forward to more great work from you, sir. Haha, I'm off to fly! Sent from my SAMSUNG-SM-G900A using Tapatalk

Nice! Very quick turn around with this! Question though, is it something can can be cut and pasted into a specific file? If so, can you provide the file name and new code, please? For the time being. Sent from my SAMSUNG-SM-G900A using Tapatalk

That worked, thanks

So, after doing some testing, here is what I learned. First off, to talk about the delivery, for the CCIP I chose to do a 10* Low alt high drag and 30* dive bomb profile. All with TAS selected. 10* was started at 2K 350KIAS with a push over at 1.8Nm 30* was started at 8K 350KIAS pull down at 2.0 CCRP I only tested 30* delivery I tested deliveries at 1.0G <0.8G and >1.2G constantly monitoring the load factor through the delivery. CCIP I found that with strict adherence to holding 1G my CEP for dive releases was <50' my best guess was 20-30' over 20 releases. I concluded that my the CCIP is a very accurate delivery when released at 1G. At more or less that 1G, my CEP rose to over 120 over 15 passes. With noticeable lateral and very noticeable longitudinal lateral deviations. Longitudinal deviations were consistent with positive or negative G on the jet at the time of release. My findings on CCRP were in line with the CCIP findings. Noting a similar CEP (~80' 1G / 200 at not 1G). This was mitigated in later releases with ripple release 4 at 10M spacing. I noticed much more lateral deviation in the CCRP passes, probably caused by pilot error. All in all. I found that when employed well, the mission computer provides a VERY accurate release solution IN A DIVE. I did not test level deliveries. I would go through and test this for yourself. I learned a few things doing this.