Wrench

Dang... Well hey, I appreciate all the work to keep this mod up and running.

tacca, The new NVG does look really good, tbh. But what I'd really like is to have nods for only one eye in VR. Is that doable with ED's implementation?

Nolan has said it's the closest he could get to a proper 109. That's why I put the name in quotes in the write-up.

Hey all. So I really liked Dunkirk (The movie, not the evacuation) It actually inspired me to start flying WWII again. I know it's not the most historically accurate movie ever made, but it's no Braveheart, either. Anyway, The "109" in the film have a very distinct Livery, so I thought I'd see what I could do to replicate it. One error is the wavy pattern on the edges of the two-tone. I was far too lazy to fix that, and figured you'll never notice it in flight. :music_whistling: I also used wildw1ng's "Hoheitszeichen" Mod, Given that I'm not prone to historical censorship. **Edit** So I fixed a few errors and fixed the wavy lines I was hitherto too lazy to do. Screens: So here's the main reference image, taken from Warbirdsnews.com: I a made Hand-Painted Version and a Procedurally Generated version since I'm not that good at painting. Screens: It's nothing special, but it's all set up for JSGME if you'd like to try it yourself. **EDIT** Added attachments. Had to separate the two to meet the forums' file size restriction. BF109 Dunkirk Skins-Painted.zip BF109 Dunkirk Skins-Rendered.zip

So I think I got it figured out. I had inadvertently put the formation before the escort. They *seem* to behave now.

Nope, it's not that. I made this mission so I could fly a spit. I've flown the route and had plenty of fuel left. I used maybe 10% of the main tank when the RTB. I'd also like to add that there is some profanity hidden in the mission file. Specifically, in the title of the AI task I tried repeatedly pushing.

Hey all. I'm working on a simple escort mission, and I've got some spitfires that are supposed to escort bombers. The problem is, they RTB about halfway through the route while the P-51's I have follow them all the way. I've tried this on Normandy, as well as NTTR. I've even tried a continuous action to push the escort task, with no change in behavior. I'm not sure why that is, maybe you guys can shed some light on this? I've attached the .miz so you can have a peek. WWII Bombing NTTR.miz WWII BOmbing Test.miz

I did a similar test before work this morning, and it was glued at 45 fps. Didn't drop below that once.

Thanks for the replies, guys. I wouldn't point to a particular time code, it's just generally unacceptable performance. If someone posted a YouTube video that looked like that I wouldn't watch it. What seems odd to me is I've recorded robo recall and hot dogs, horseshoes, and hand grenades, and those look fine. Seems a DCS issue. I've seen videos of DCS on a rift on YouTube that look far better than what I'm getting.

Finally got around to a video. It's a pretty horrible video, in every possible way, but it illustrates the point.

I doubt it. It really doesn't take any GPU horsepower since it's merely displaying what's in your left (WHYTHELEFTDARNIT) eye, so it isn't rendering anything extra. All its doing is sending the same image to two places. That's what I wanted to do, but the repeater/mirror looks awful. I'll post a video ASAP.

Yup, I mean what's displayed on the monitor. (Repeater might be a better term)

Hey everybody. I'm having an interesting issue with the Rift. I get really good performance out of my rig (details later) in the Rift, but the On-Screen Mirror is awful. It gets like 10 fps and the headtracking seems super jittery. I'd like to record/stream DCS, but not like that. If anyone wants to see I can upload a video a little later. Does anyone else have something like this happen/is there a solution of which I'm unaware? My Rig is pretty decent, I have a intel i7 7600k @ 4.2 MSI GTX1080Ti 11GB 16 GB ram @ 3000 DCS installed on Samsung SATA SSD I have tried the settings using the 'VR' base settings and turned the textures to HIGH so I can actually read the text. I also have the pixel density at 1.5 (as recommended in every video I've seen) but it doesn't seem to make much difference if I turn it down to 1.0.

It's not...not possible. I wouldn't hold my breath, though. ED has considered the A-10C done for a long time, its unlikely we'll see any updates any time soon.

Hey Ciribob, Got an audio device error on a new headset I got. I got a Steelseries Arctic 5, and I'm having trouble with one of the two devices. Thea headset is seen logically as two devices to provide a game/chat mix knob. When selecting the "Chat" version, it works just fine, but when selecting the "Game" output, SRS crashes. I'd like to be able to use it on the game output for recording purposes. Anyway, I cleared the log file, launched, selected the device that isn't working, and enabled preview audio, to get the crash in the log. For your convenience, I've provided what I assume are the most relevant lines. 2018-01-01 04:40:26.8282 | Ciribob.DCS.SimpleRadio.Standalone.Client.Audio.AudioPreview | Error starting audio Output - Quitting! Exception from HRESULT: 0x88890008 System.Runtime.InteropServices.COMException (0x88890008): Exception from HRESULT: 0x88890008 at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at NAudio.Wave.WasapiOut.Init(IWaveProvider waveProvider) in E:\Dropbox\Dev\DCS\DCS-SRS\NAudio\Wave\WaveOutputs\WasapiOut.cs:line 366 at Ciribob.DCS.SimpleRadio.Standalone.Client.Audio.AudioPreview.StartPreview(Int32 mic, MMDevice speakers) Please see the attached log. Thanks as always, Wrench clientlog.txt

Snoopy, interesting point. I knew the later versions had an HMCS of some type, I just assumed it stole the system from another aircraft like it did the stick and throttle.

The only thing I wish we could have is a JHMCS. Given the TGP, or even the TDC for that matter, takes some time to get on target if you see it with the MK I's, It would be nice. I read in a thread some time ago the JHMCS was specifically forbidden from modeling in the contract, a BS "Center screen SPI" or "Slew (sensor) to LOS" would be nice to have.

That's easy enough for the community to mod in. Given how ED is uncommonly supportive of its modding community, it certainly will be.

I can tell you something has changed. At least, I think so. It had been over a year since I last attempted Air-To-Air accidental high-fives of a tanker (commonly known as failing to refuel) and in the last month or so I've found it to actually be pretty easy. In the interim, however, I've gained a lot of precision, formation, and general flight experience than I had at last attempt, as well as I now use a Thrustmaster Warthog as opposed to an ancient [\i] Saitek X45. In any event, I can now pretty consistently refuel from 3000 Lbs to a full tank in one go. I'm not sure if its the hardware, wetware, or if the software has changed, so I'd kinda like to know if anyone is aware for certain of any software changes that may have been implemented.

Ah, okay thanks. Must have missed that in the manual.

So we all know that when employing the gun, the HUD will display impacts using small circles that pop up where the rounds are actually hitting. I've been wondering about this for a while, how does IFFCC know where the rounds impact to place them? I have to assume that it has a sensor (TISL, maybe?) That detects the IR signature of the HEI rounds explosion, or similar. In any event, I'd sure like to know. Wrench

Like I said, I understand it can't be perfect. I just wish it would stretch the image linearly, rather than an exponential increase of distortion from the center to the edges. I understand that zooming in will reduce distortion, but given I sit 2 feet from a 34" curved screen, that feels much too claustrophobic.

It doesn't seem to make too much difference. I'll leave it there though, given that's what it's supposed to be.

Yeah, I had only just posted the video. Should be up proper by now. Essentially, the sides of the screen are much more stretched than the center, making it pretty obnoxious. I've tried editing the snapviews.lua, but that really didn't change anything. DCS reports 3440x1440@2.38888 aspect, which should be correct. I think I'd actually prefer the whole image be stretched evenly, even if that does distort the whole image, at least it would be consistent.

Hey guys, I posted a YT video of some issues I'm having in 21:9 aspect ratio. I'm hoping one of the magicians out there can give me a hand. ${1}