Guppy

I sell my plans for $100. All you need to do is submit them to a CNC Routing company and they fabricate them. feel free to PM me.

I'm noticed improvement in the SP PG Freeflight mission. There is still FPS loss, but just a handful of frames... 5ish. I plan to do some testing this evening on MP. I'll let ya'll know my findings.

:doh::megalol:

Thank you! I'll do some testing if/when that patch hits.

You're better off getting some a little bit larger and building a case around it. I have a blog going in my signature, take a look and hopefully be inspired.

Nineline, here you go. Singleplayer stock Persian Gulf Free-flight Mission (20-40FPS shift): A note on this, I have only DCS running and it is running in fullscreen mode. I kept it as vanilla as possible... obviously if you know me at all I usually run a bunch of exports and stuff. 60FPS normally; 40-50 with SA page up. This particular track you'll see me way into the 100s for FPS. But the swing is substantial (20-40+ FPS differences). https://drive.google.com/file/d/1WjhwvOhG2ml1XkUp_KtfZQaCe_r3NmaC/view?usp=sharing Brief MP mission demonstrating frame-loss in VR: https://drive.google.com/file/d/1-ZI-Ryi8U8zCMWT9k01kqNYX1x4lglXE/view?usp=sharing I've enabled sharing so anyone with the link can access it. If there's anything you would like me to test - please do not hesitate to ask.

I get massive drops in both MP and SP. regardless how much stuff is in the mission.

SA Page Performance Reduction - Its Back Seeing a 25% degradation in performance between turning the SA page on and Off. Here is a very short track in MP seeing this. 8700k@5.3; 2080ti; 32gb RAM; SSD; HP Reverb https://drive.google.com/file/d/1BTrGfaxlfdwrb2SJzO7-Q3WUnz9CoJ_k/view?usp=sharing

AWW-13 should be getting modeled. https://forums.eagle.ru/showpost.php?p=3285514&postcount=13

NineLine - I agree. Can you please follow-up with the team and speak a little bit about the effort you suspect it will take to get it from the Viper into the Hornet after it releases? Are we talking a week? a month? Two months? Is it unknown? When I go back and read both yours, BN and Wags' messages on this topic it sounds relatively quick. This sort of goes back to my original premise of managing expectations. This would help me and others, I think.

This is why Engineers are frequently not customer facing. Optics and context matter. What ED did is they failed to properly manage customer expectations. Had the communication been better we would have known the radar guy was prioritizing the Viper over the Hornet. Based on communication I have read it sounded like all the Hornet devs were back on the Hornet. This was not the case. So finding out the Viper radar is advancing further and faster than the Hornet killed my expectations. Reading a bit between the lines It sounds keeping the radar guy on the viper shortens the overall tail to the timeline at the cost of delaying the Hornet progression. This makes sense, BUT explaining to your customer WHY this is the better path and WHY a 1-month-old module is getting a feature over a 1.5 year old module matters. If we saw something like the attached imagine to explain this... it would be clear as day. Especially on a title that has been out for 1.5+ years. This would be a no-brain'er; in my hypothetical example...we gain 2 weeks of development capacity with this decision. I deal with this type of communication all the time. This could have been managed and articulated better.

(Referring to the quote below) This is the problem: This should have been super clear to us Hornet owners since the beginning. This explanation completely makes sense to me. I do not like it and it upsets me, but I understand it. I work in App Dev (different industry) and understand why this choice was made. However, I'm a bit more tactical in how I communicate information like this. Randomly seeing a FB video of the Viper getting TWS and no additional context or why... is upsetting. Especially when we look back at the history of "Viper won't slow down the Hornet". While to you (ED), it might be true that Hornet progress is marginally slowed down (or not at all), it does not feel that way as a customer. It is your job to manage our expectations, for us to know your vision, but the way you all are communicating this information... it's just really, really difficult to understand when a new Viper video drops on a feature that has been wanted for the Hornet well over 1.5 years. Be transparent, but please be a bit more tactical.

I'm not sure if it is required... but I did successfully use it on Sunday when I had both BALT and HSEL selected.

Copy, thanks! Hopefully a little light at the end of the tunnel!

Very disappointed with the hornet progress through summer and now into fall.

Virpil, hands down. 1) you can actually get your gear in a realistic time frame 2) the quality of the products is similar. 3) pairing with TM grips is far easier. So if the quality is similar just go for what you can actually get.

- First: they hear nothing, but your radar likely appears on their RWR - Second: (assuming you have LTWS on) they hear nothing, but your radar likely appears on their RWR; you are "soft locked" onto their track file. But you cannot hand off the track to your missile if you launch. Basically this helps you track other target while having an idea of additional track information on the target you locked. - Third: You are locked onto them and they will more than likely be getting RWR lock tones.

HJP - For IKARUS there are XML files that essentially communicate from IKARUS to DCS. Are you able to release the F-14 XML ahead of the graphics? This is will allow me to start building my own switches/buttons for my custom UFC. Let me know!

If given the option, which it sounds like we will, I will certainly be having fun wielding 6 mavericks into battle. Unless, of course, there is some sort of damage that occurs. #Destruction

Warranty-Schmoranty. Whose got time for those. :joystick::megalol:

You are not the first person to experience this. I had the same issue. On the metal grip there are 3 screws, unscrew them and pull the pin out from the paddle switch. The metal grip will now split in half; take the cover off. Just like the WH, there is a grounding hex screw that holds the silver shaft to the metal base. Just tighten this. Mine was not screwed in fully. I added a little adhesive (that loosens when heated) to keep it from loosening, but it's not needed. Reassemble... and bam. no wobbling

Yep - it's definitely that code... it's the 9 at the end. Thanks all - I appreciate it.

This might be it then. I’ll need to confirm - I think the code I was entering was 1689.

Google Drive link with Track of the described bug: https://drive.google.com/file/d/1_xkwe2JvkxKYMfU4omR0vvu2fENVpHX9/view?usp=sharing

Take a look at this: https://guppy.home.blog/2019/02/06/configuring-screens-and-pulling-data-from-dcs/