Jarhead0331

This is actually a really good point that seems to have been lost in the shuffle. They were either not being forthcoming then, or they are not being forthcoming now. This just goes to my point that the decision to delay again on the ground of "MP functionality" is illogical and doesn't make sense. There must be something more. I just don't understand why they can't be honest...and well..."transparent" about it. As I stated previously, I'm not happy about a delay, but if it doesn't work, it doesn't work and it can't be released. However, communicate it better, honestly and in a more timely fashion. Also, the announcements about an imminent announcement have got to stop. Just make the announcement once. You'll spare your customers the apprehension, anxiety and aggravation that builds in between. This is really just common sense. Finally, on the issue of transparency...saying you are going to be transparent is just lip service. You actually have to do it.

That is a ridiculous response to a serious, mature expression of another person’s opinion. What are you, 12?

Why does one need to take one position or the other? Doesn’t someone have the right to be pissed and understanding at the same time? Speaking for myself, I’m really disappointed that the release has been delayed. I’m also really annoyed that news of the delay was conveyed the morning of the anticipated release with not a whole lot of detail about the actual reason for the delay and no new commitment to a future release date. That is a really bad sign. At the same time, if it’s just not ready, it’s just not ready, and if it doesn’t work, then they can’t release, and I understand that. So, in that regard the decision to delay is also practical and perhaps unavoidable. $hit happens, we have to deal with it. What I don’t understand is all the accolades that go out to “Kate” for making some statement on the morning of release that includes a little more information on a general development roadmap. Whoopty doo. Until yesterday, I didn’t even know who she is. She barely interacts with the community here and I’m hard pressed to view the single post as “transparency”. That honestly rubs me the wrong way much more than the actual delay. I mean the whole announcement about an announcement makes no sense. It created much more agitation then necessary. I’m just flummoxed by all the ass kissing over this announcement. Sorry if I do not accept it at face value, remain skeptical and expect more. Ive been with this sim since the beginning. I’m not going anywhere, but I have a right to be put off, and I won’t be apologetic for my disappointment just because the CEO who I’ve barely ever heard of made some general announcement.

Just like that, the single player crowd gets the shaft. I don’t really follow the logic. If the cause of the delay is true, and it functions acceptably in single player, why not release. Isn’t giving everyone something on time better than giving nothing to no one? It would at least let both the SP and the MP crowd learn how to use the module while waiting for full functionality. My personal hunch is that the problems are deeper and more complicated. Where is Wags, for instance? Why no videos?

Who is "Kate" and why have I never heard of her? She sounds important. I've only been with this sim since the LOMAC days. lol

Why on earth even make an announcement about an upcoming announcement? I mean sweet baby Jesus, just make the announcement when it's ready. Why go out of your way to piss people off twice?

Thanks for bringing up IPD...it is a subject I do not know much about. Do I need to actually measure my own personal IPD and then input that setting? Right now it is set for 63.5, but I have no idea if that is what it should be. Thanks.

9th generation i7 with 32GB RAM and a 2080ti with 11GB RAM. I wouldn't expect system performance to be a factor.

I'm looking for some advice on making the transition over to the Reverb. I've been using a Rift-S and have been satisfied with it as a VR platform, but was urged to pick up a Reverb due to all the high praise on clarity. So far, I do notice some positive difference, but I can't say I am "blown away" like many others seem to be when switching over. Hopefully, this is just a settings issue. I've gone through the recommendations from Thud's page, but might be missing something. Basically, some of the cockpit gauges and dials still blur at times. If I push the headset down on my nose, clarity improves. Is it just a simple matter of not wearing the headset properly? Also, at times, I notice some kind of a peculiar "pulsing" type stutter. I'm not really sure what could be causing that... Any suggestions on making the transition to this new platform smoother would be appreciated. I'm close to just going back to the Rift-S, which was enjoyable and trouble free.

Ugh...still no VR optimization!?

LoL...where were you a week ago. :megalol:

Reverting to a single monitor from the a10c virtual cockpit and moving down to a 4K resolution seems to have solved the problem. Still find it interesting that the export setup only negatively impacted the Hornet DDIs. Anyway thanks to everyone for all of your helpful suggestions.

This is likely not the issue since the problem is only with a single aircraft and not others.

When I fly in VR the DDIs do not export. The export monitor goes black. I do not change any other settings.

Changed stroke thickness and fuzziness settings in the MDG_strokesDefs.lua file and this definitely helped. Its still not super clear and some digits are very hard to read, but, it is definitely flyable, whereas before it was not. Before: stroke_thickness = 0.8 stroke_fuzziness = 0.5 After: stroke_thickness = 0.3 stroke_fuzziness = 0.1

I changed the pixel desnity to 1.5 and changed MSAA to 4x and SSAA to 2x. This has improved the overall graphics quality and even sharpened the MFDs in the Harrier, but it has not improved the problem with the Hornet DDIs...any other thoughts?

^Thank you. I will try that.

^I'm using a Rift S. I have a Vive and will check if the problem persists with that HMD. What is PD? Sorry...:cry:

I have this same issue. I usually run the driver install in the support folder to get the image back.

I have a weird issue with the Hornet in VR...the left and right DDIs are completely unreadable. The text on them is blurred and blocked out...zooming in does not help. It is an odd problem since I do not have the issue in the AV8b...it just effects the Hornet, and only the left and right DDI, not the MPCD. I do have the DDIs exported to a small 11" monitor with cougar MFDs for non-VR play when I fly with TrackIR. I presume the lua file for the export might be the source of the problem, but why only the hornet and none of the other aircraft that also use the exported DDI/MFD? Any feedback is appreciated. Thanks.

You guys could have saved yourselves a lot of time had you just listened to a few of the forum experts, instead of relying on real pilots and engineers. Oh well, better late than never I suppose...:joystick:

The Mig-19 can kiss my lily white behind.

I think the heart attack is much more likely to come before you get the opportunity to shoot them down. It will probably come when they cannot figure out how to start the engines. :pilotfly:

The level of butt-kissing and coddling from the fanboy brigade in this thread has reached epic proportions. Bravo! As if to say Heatblur and team are not in this for profit in order to run a successful business, but rather are doing all of this as a big favor to the community; a labor of love, if you will. Give me a break. Heatblur is selling something for profit and they have accepted money in exchange for its promise to deliver. When you accept money, you enter a contract, which creates certain obligations, both express and implied, including a covenant of good faith and fair dealing. Now, for the record, I have not and am not suggesting that Heatblur has violated any obligation, or breached any obligation to the community, or the customers who have paid for the module. However, it is absolutely offensive and preposterous for members of this community to attack, insult, belittle or ridicule other members of the very same community who have simply asked for specific, unambiguous, non-contradictory information on the status of the module and when it is expected to be released, or those who have expressed frustration over the present state of circumstances. Those of you who have espoused the, "take all the time you need" philosophy to consumer relations have absolutely no right to dictate to others who have spent money on this module, what to say, what to ask, how to express themselves, or what to expect based on statements that have been made by the development team over a period of years, but more importantly, over the last several months. What gives you the "moral high ground"? You are simply the opposite end of the extreme, and are, therefore, equally annoying and obnoxious. Everyone who is taking the time to read these threads is obviously committed to a successful release of this module. We literally all want the same damn thing. Some of you are happy to tell HB to "take all the time in the world" to release a perfect, bug-free module. Others, prefer a different approach. Neither group deserves to be ostracized, but it seems to me that those who prefer to grant carte blanche to HB are the only ones casting insults and criticisms. Grow up! Seriously, if it wasn't for threads like this, and the ceaseless back-and-forth, this subforum would be nearly dead. Think about why that may be...

Wow, Moonshot. That is all very troubling. I had no idea this thing was supposed to be released in 2017, with "no exceptions..."