j0nx

My avatar's expression sums up perfectly how I am feeling with ED these days...

HAHA riiiight. Just like cockpit updates and other misc upgrades to existing modules are right around the corner :music_whistling: I may stop by microcenter otw home today to grab one of these but still not sure it's really worth it from a clarity perspective compared to my cv1. If it's going to destroy frames then I'll pass.

How's the odyssey plus compared to the oculus as far as clarity? I've been thinking of upgrading my oculus rift to the new model S or to an Odyssey plus.

Are we ever going to get this update and fix the problems with the shark? It was supposed to be by end of year 2018 and now we are almost into June and still nothing. I'm starting to get annoyed here.

Well said! :thumbup:

I'm pretty sure ED has shown you their priorities: fighter jets These jets have taken priority over everything for a year now up to and including the game engine itself. Everything but the jets has gone by the wayside.

Come on! They been busy with all these jets! The F18 and F14 aren't going to make themselves. :music_whistling: Good for jet guys I guess but not for guys whose modules have been broken since 2.5.

I don't care if it's free or if we have to pay for an updated module. At this point I just want the updated module instead of all these perpetually half-finished fighter jets that ED keeps spending all of their time on these days. The F18 and F14 have completely consumed this company at the expense of everything else and I can't say I am happy about it.

I've used their Bell 206 collective for about 5 years now and love it. I want to order this as well but I find their shipping fees to be too much especially with the product already at almost $800US. The shipping puts it out of reach.

All I am saying is that when I drop collective and drop 500 feet straight down and then 10 feet from the ground pull collective and gently land then something isn't right. It makes me question everything else about the flight model at that point. It feels more like a ship from battlestar galactica to me than a helicopter if it can do that.

NM, I just noticed the other 20 page thread in the root directory. Yikes. Looks like I'm not the only one. Please delete this thread if you want.

I haven't spent too much time in this bird but it doesn't appear to me that VRS is modeled and the flight model in general seems more gamelike than sim. I dropped straight down 500 feet and then lightly pulled collective to gently settle to the ground. I thought for a second I was in FSX. Am I the only one?

I just bought a 2080ti and now when exiting from DCS while playing in Nvidia 3D, it causes a black screen at the windows desktop requiring a reboot. No idea if this is a driver problem, card problem or something with the new update but wanted to see if anyone else was experiencing this?

I’m not sure what that has to do with anything anyway since the crashes started right after the latest build.

SOME stability issues? I would say lots of stability issues. I may have to opt out of the beta build unless a fix comes soon.

I got fed up lastnight and did do a clean install and it already crashed with Huey when Huey crashes with hard landing. No lockups yet but no time to do thorough testing yet today. This new pc can do hours upon hours of prime 95, handbrake and unengine heaven stress testing and benchmarking without issue so the clocks are definitely stable. It started right after the last patch. I played for a few hours the first night with this new pc on the previous build without issue and the problems all started after I updated with this patch. Shrug.

Not true. Just reading through this specific forum there are multiple folks other than me getting hard locks after this patch. Sometimes it crashes to desktop and other times it locks up which causes me to have to reset my PC. Others here are seeing the same behavior.

Crashing the huey causes the sim to crash. The last beta patch is a debacle so far. I have never had issues like this in a patch since they removed all the autogen from NTTR about a year ago.

Mad crashes here with new pc build. Was thinking it was something with the motherboard but it's only happening in DCS from what I can tell. Sometimes it crashes to desktop but most of the time it crashes and then about 30 seconds later my entire PC freezes with a solid hard drive light. Thought at first it was my drive going bad but swapping it out and I am still getting crashes. This all started with the new patch which came out coincidentally one day after I built this new PC. Is there a patch coming out to fix this patch?

Add me to the list. 2 hard locks within minutes since the patch was installed. No issues before that. Actually mine may have been due to a 6+ year old ssd drive going bad. Same thing happened in xplane with hd light on solid. I swapped it out and will see if that was the culprit or not.

My Corsair HX1000 PSU is about 10 years old and has been serving me well since my 920 build. At least 3 or 4 upgrades in that time up to an 8700K I am about to upgrade to on that rig. Frankly every time I put a new board in that PC I am surprised that PSU is still ticking. It was also turned on 24/7 for at least 7 out of the 10 years it's been running. That being said, it will probably fail on me now!

Keep getting the following error when I try to start key emulation on version 2.7.14.: 1073 element already has a logical parent. It must be detached from the old parent before it is attached to a new one. I can use version 2.5.1 fine. Seems to be related to the PZ70 autopilot module. Any ideas?

Setting the monitor to primary is only way I know. Only takes a second to right click the monitor in the nvidia control panel and make it the primary. Word is that big picture mode in steam allows you to select which monitor to output to but I have never used it and wouldn't apply to you unless you are using the steam version of DCS.

Hard to do when you spend 90% of your resources on the !@!#$! F18. I would sure like to spend more time in the shark but not worth the effort until it is fixed.

Did that. Didn't work. Ended up having to delete registry key and reactivate all modules. Nasty bug apparently that is at least 8 years old now...