pimp

Whats your current Shadows setting?

For single player missions, I want to ramp start in certain spots. I know by blocking certain spawn spots you can manipulate where you can ramp start as a player. Is there a way to do this using templates, because I created a template that blocks the 6-pack, but when mission starts, I'm on top of the static object. However, if I insert a static object through the mission editor I spawn where I want to but that static object isn't part of the template. Therefore, my Remove Objects Template can't remove those static objects. Is this even possible?

I'll definitely give this a try in VR, although it seems like you improved just the static rain drops and not the dynamic rain drops. Thank you for this mod. I've been crying about this issue in VR for almost 3 years.

I believe this is a DCS issue and always has been. It's not only VR tho. Objects popping in & out of view based on moving your head slightly happens in 2D also. Just take a look at Wag's Carrier video starting ~4:10 Sidewinder pops in & out of view Now getting responses from ED regarding VR issues is another story. This is ONLY MY OPINION but I feel like VR is ED's step-child. It doesn't get the love I feel it deserves. I personally believe they need more employees that are dedicated to specific tasks. For example, a dedicated VR engineer. Whoever is the engineer on VR is also working on something else which means certain VR issues gets put on the back-burner or low priority list. For instance, this nearly 3 year old issue regarding the new rain drop effect still hasn't been fixed, VR New Rain Drop Issue. This also happens for the AI. The AI engineer also works on the Hornet's Systems and the new ATC Comms. So no telling when the AI will get a long overdue improvement.

I just wanted to update this thread. I got this working now. I just removed the other M.2 drive and inserted my new drive into M.2_2 slot and installed windows again. It's been a week so far so good.

Thanks. Yeah I'll definitely give it more time, but I'm not selling my G1.

Yeah I didn't expect a big step up. You had already mentioned that to me a while back. However, I did expect the improvements to justify another $650. I did see an improvement with the colors. They do seem a bit deeper, but that along with the audio was just "eh" to me. The on-ear earphones sound better IMO. Although I am impressed at how well they sounded to be off-ear. IDK WTH they were thinking with the Rift2. That was atrocious. I don't use controllers at all so no comment there. My IPD is 67.5 and it's a hassle to get it close to it. But to each his own I guess. I'm still open for suggestions tho.

I'm sure Pilots use it in an overcast weather scenario since TGPs are useless when clouds are a factor.

Even though it's only been setup for less than 24 hours, I regret to inform that I am not that impressed with the G2. I can understand those that come from Oculus-->G2 seeing a really nice overall improvement, but I'm coming from a G1 and the improvement is very marginal. The only improvement on the G2 I really like is the new cable. That's really the achilles heel of the G1. That thick ass cable contributes to a lot of the issues with it. I was expecting a bit of a WOW factor regarding the clarity of the G2. Although I do see an improvement, IMHO, it's negated by the smaller sweet spot. In my G1, the SS was set to 150% with nice performance. In the G2 it's set to 80%. When using the same DCS settings, I get a noticeable performance hit in the G2 with frame-times often in the mid 20s(Red). I was really holding out to even consider getting a G2, but when I found out that I'm still at least 2 months away in the EVGA queue from getting a 3090, I decided to jump on the opp to get the G2 since it's available. So unless you all can let me know if there are some more settings I need to change, I will more likely be sending back the G2. The improvements over the G1 are just not worth another $650. I believe my G1 paired with a 3090 will be a match made in heaven. I'm still testing so any suggestions to help with performance will be appreciated. I at least want to match my G1's 150% SS quality and performance. Steam VR Settings: "motionReprojectionMode": "auto" SS: G1-->150%, G2-->80% App multiplier: 100% DCS Settings: VR Pixel Density: 1.0 Shadows: Low (I modified the shadows.lua. I have Medium outside shadows & Ultra cockpit shadows.)

Received my G2 today. I'm going to set it up this weekend and see what all the hype is about.

Nellis AFB on the Nevada map.

Why are people expecting clouds in this patch?

Knowing that ED has limited resources, I still wish they take a break from modules and spend at least 6 months on AI improvements. ED makes improvements here & there, but it really needs a compete overhaul. This sim would be 90% better all around. Unfortunately, I believe there's only one engineer that works on the AI and it's the same engineer working on the Hornet systems and later the ATC comms. So I don't think the AI is that high of a priority for ED, IMHO.

Thanks for the heads-up. Hopefully I get by this weekend.

I blame you for my recently purchased G2.

I see the G2 headset is available to purchase and ship. I was really wanting to wait until I get a 3090 gfx card before looking into getting a G2 since I already have a G1. No telling when the cards will be available. What to do?

So I said F it and performed a new Windows install with the new memory. After a successful installation, I restarted my machine and the exact same issue happened, BSOD. Is there some kind of incompatibility with the memory and my mobo? I am so pissed. I guess I'll just have to return this memory and continue to use my original 32GBs. Any help would be appreciated.

What video?

The moderators can put flashing lights around that thread, and people would still ask about a patch update.

Resetting bios via mobo. The latest bios version is installed.

Hi All, So I received the M2B version of 4x 16GB sticks. I installed one kit, cleared CMOS, entered BIOS, and exited BIOS. No XMP profiles were loaded. Everything was set to defaults(Auto) with memory speed of 2133MHz. The PC booted to Windows successfully. However, when I restarted, I received the blue screen in my original post. When I "Press Enter to try again", I received the screen below: The application or operating system couldn't be loaded because a required file is missing or contains errors: winload.efi. These are the same issues I was having before. Again, if I choose to "Press ESC for UEFI Firmware Settings"(BIOS), I can enter BIOS and just exit out and the PC boots to Windows. I've checked for that winload file and it does exist. I can't even start Windows in Safe Mode. I get these blue screens. It seems like if the RAM my Windows install was built on is not the only RAM in my machine then Windows has some issue. Any and all ideas on a solution is welcomed. Please let me know if you need more info. Thanks in advance!!!

Yes you do, but ED just bundled the Kuz with the SC. All I'm saying is that I'm not surprised it's not to scale. It's just an updated LOMAC model.

Probably why it was free. The free Stennis was not to scale either.

Thank you both for your replies. I feel stupid because I noticed this difference before, but did not think much of it. My original 8GB sticks have serial number CMK16GX4M2B3200C16 which can be found on the QVL for this specific mobo, however, the 16GB sticks' serial number is CMK32GX4M2E3200C16 which I just realized is not on the QVL. So I will be returning these 16GB sticks to Microcenter near me and I just purchased the correct 16GB sticks, CMK32GX4M2B3200C16, directly from Corsair. Not saying this will fix my issue, but I at least want the correct parts before wasting people's time. I'll keep this post updated once the new RAM is installed. Thank again.

Hi All, I have 32GB(4x 8GB) of RAM and I recently decided to add more. So I installed 32GB(2x 16GB) of the same RAM type and removed 2x 8GB which totals ~ 48GB of RAM. After installation, I could not get my PC to boot up. The white LED(VGA boot) stayed on so I cleared CMOS and was able to get into BIOS. I applied my XMP II Overclock Profile for my i9 9900k, saved settings and restarted my machine, but I keep getting the error screen below. From that screen, I can get to BIOS and just exit out and my machine boots up successfully. However, every time I restart my machine or cold start, this blue screen shows and I can just repeat the process of going into the BIOS and exit. So I decided to purchase 2 more 2x16(32GB) sticks to total ~64GB because I figured there was a conflict between the 16 & 8 sticks. So after installing the 2 new 2x16GB sticks, clearing the CMOS, and reapplying my XMP II Profile, the same issues occur. The blue screen shows, I enter BIOS, and exit BIOS to boot successfully. As a test, I reinstalled my previous 4x 8GB sticks, cleared CMOS, applied XMP II Profile and restarted successfully. I can keep restarting or cold starting multiple times without getting the blue screen. So I’m not sure if my machine just does not like this RAM or it just can’t handle being upgraded on top of this existing Windows install. I also thought my overclock profile was an issue so I set all my settings to default, but the blue screen still happened, but not on every restart/cold start. I haven’t attempted a recovery/repair yet since files can get lost. I wanted that to be my last resort. Some assistance with this issue would VERY much be appreciated. Please let me know if more info is needed. Latest Main Specs: i9 9900k @5.1GHz Asus Z390 E-Gaming Corsair Vengeance LPX 64GB DDR4 3200MHz Samsung 970 Evo 1TB Windows 10 Pro Build: 19042 (month old new install)