Willie Nelson

Ok, Like others have read and re read the CPIS information that was linked in the quick start guide and although I have the flight director roll bar working pretty well I cannot for the life of me get the pitch bar to work even though I have successfully selected on the ALT mode (speed between 70-150 kts and Vertical speed +/-200 fpm) the light for altitude hold comes on but and the collective command indication shoots up but the pitch bar remains asleep at the botom of the vertical situation display (which any other aircraft manufacturer would call an AH) perhaps this has something to do with which "sub-mode" it is in, but the only selection that I am aware of is ALT. The same goes for the ILS mode, I can see a valid ILS signal displayed on the VSI howeverwhen I intercept the GS, after successful intercept of the LOC, the pitch bar does not show useful information and the collective command indication is does not make sense either. If this is simply a bug at this point, no problem at all but ususally it's just me too stupid to figure it out. Again, awesome mod. I have been waiting for this mod...like....all my life!

That will no doubt be it. I don’t remember doing that. Thanks heaps.

I did a cold start and noticed the "Stabilator" warning light was on the caution panel so I manually trimmed it to full down as I understand that is what is required for takeoff. I could not find a way remove the caution on the panel, so I took off with disastrous results. As airspeed increased, sure enough, the nose went low and was unrecoverable. Can someone elaborate on why I had the stabilator caution light on, I did endeavour to follow the cold start procedure but I have obviously missed something.

Just installed it..........flew for 30 minutes. Friggin awesome! I knew nothing of this and it looks and flies fantastic, proper vortex ring state that you can't just easily power out of, decent propensity for dynamic rollover, good looking interior and exterior. I'm going to have some fun with this bad boy! Only problem is now I have to get used to AAR in another machine, just when I wsa starting to get the Viper sorted!

I hear you. And I suspect that you’re right, I just hope you’re wrong, this machine is a beast and I’d love to see it given respect and licensed properly. Let’s hope you’re wrong.

I’m really interested in this one. I hope it’s developed into a payware mod with full PBR and full flight model fidelity because this chopper is awesome. Hopefully it gives either ED or other developers the encouragement that they need to properly roll this one out. as yet of course, I haven’t had a chance to even look at this version because of work and family commitments but it sounds like a cracking start. Their are plenty of us I would imagine, who don’t always feel the need to fly combat operations but simply love flying authentic chopper mods.

https://uploadvr.com/xtal-3-ces-hands-on/ Not too many of us mere are going to be happy to shell out 10k for a plastic VR headset. Having said that, it’s great to see that not only is the technology available but it’s likely going to transition to retail customers in some form or other. Thoughts!

No, Single monitor plus a Reverb Gen 1

Pretty much says it all in the tittle. I did solve this myself however and this is simply a community service announcement for those who end up with the same problem. The cause was me thinking it would be logical to try select “Use DCS system resolution” under VR Mirror Options. Do not try this at home kids, at least not if you’re using a WMR Reverb like me. Because I couldn’t change any settings, I had to go into the VR settings via the USERS/your name/Saved games/DCS/CONFIG/options and change “[“mirror_use_DCS_resolution”] = true,” to “[“mirror_use_DCS_resolution”] = false,” Problem solved. That is all.

I’m having this problem too and I haven’t changed any SteamVR resolutions at all. The two suggestions mentioned did not fix it for me.

Actually, the solution was not as I first thought. At some earlier stage in the Viper rollout you used to be capable of inducing a hot start by bringing the fuel prior to the recommended 20% RPM. That has more recently been changed and now if you attempt to introduce fuel it will be inhibited. That was at least in part the problem so don't attempt to bring fuel in anything less than 20%.

I’m sure that there are some limitations with what has been done so far, there probably always will be. If you go looking for imperfections with anything you’ll find it. I think it looks fantastic! Well done, looking forward to seeing it live. Things are progressing well.

Problem resolved, it turned out to be a calibration problem with my warthog idle cut off. My bad.

Bump

Righto, love to find out what I am doing wrong, thanks. This one seems to upload. (same problem persists) I am wondering if it is something I did in the mission editor on the "dawn raiders" mission? No fuel at startup.trk

I have been flying the Viper and regularly completing successful cold start for close to a year now however the last several attempts to start the Viper from a cold and dark ship have not been successful. I have completed a repair selecting the slow option, there was nothing indicated as anomalous during that process. I remain on the latest open beta (through DCS_updater selection at start up each time). I have also attempted to post a track file recording of the cold start tutorial where I followed the instructions to the letter just in case I was missing something obvious, I am not. The track file was too big to post despite being very short. Doesn't happen on either the Hornet or Huey and all other missions or instant action files that operate with the engines already running are fine. Happy to come back with more info as requested.

Hi Flappie, I probably have to retract my assertion. I recently did a comparison of IGE/OGE and I seemed to be able to get the aircraft to hover at 29 psi of torque both in ground effect and out of ground effect (100 feet) however when I attempted to replicate this, I could not repeat the results. So sticking with the scientific method, if I cannot replicate my results then I will withdraw my claim, sorry. In fact, moreover I held around 31 psi of torque at a 100 feet hover in the Caucus free flight instant action scenario and it settled beautifully at around a 5 foot hover, which is exactly what I would expect. So my bad, I'm not sure how I had mixed up my initial observations. Disregard.

Hi DishDoggie, Perhaps I haven't explained myself very well. I'll have another go: There is a known problem in the DCS Huey where by the torque (power) required when hovering close to the ground is the same as that required when hovering out of ground effect (IGE versus OGE). This is NOT a correct representation of the flight model of a Huey or any other helicopter. In real helo's the difference between toque required IGE should be noticeably less than that required when hovering OGE. For example at the MTOW of 9500 lbs the chart shows, in the bottom LHS of the screenshot that the torque required to lift 9500lbs will be 36.8 psi in ground effect @5ft versus 42.1 psi out of ground effect (say 100 feet AGL) this is why helicopters may sometimes "settle" when overweight but not necessarily touchdown because of the amount of lift being, in part, a function of the square root of the distance from the ground. This effect is caused by the reduction in induced drag. I am hoping that their is discussion about rectifying this missing phenomena within DCS but I have not been able to find any as yet.

I have done some searching however I cannot find if there is likely to be any changes to the unchanging power requirements to both IGE and OGE hovering. To be clear I am talking about the power required to hover a 6600lb Huey being 29 inches of torque both in ground effect and out of ground effect. I may have missed a post that has already discussed this elsewhere.

So I was having this problem on what I believe was 1.8.4. I updated to the latest version and the problem is now solved.

I have an fairly old i7700k OC to 4.8GHz and a 2080ti with 32G of ram with XMP enabled and I have to say that my DCS performance is fantastic. Not flawless of course but once I am airborne and heading off to the field of conflict it is pretty smooth unless I am passing someone head to head in close quarters. I compare this to P3D V5 and MSFS and DCS is way ahead. I can and do use the others but it is a comparative slide show. As we head toward the much feted Vulkan implementation, I do wonder if it might be a case of careful what you wish for. I'd be fairly confident that the first few iterations may be less than desirable, I hope I'm wrong.

I’m not likely to get an 8KX given I too am really happy with my Gen 1 Reverb but to the credit of Pimax, at least they’ve demonstrated that that sort of pixel pushing can in fact be done with fairly decent performance so I’m looking forward to the Reverb Gen 3 or 4

I can see why it wouldn’t be a number one priority but being able to practice formation so that you don’t look like an idiot would be really useful and doing it in a MP server like Aerobatics Online is an exercise in incommunicative Anarchy.

I'd love to see something as simple as the ability for the AI to move slowly into a turn so I could do some practice formation with them rather than trying to follow them as they snap roll to the left or right.

@FETUS That sounds like a great reason to stick with the G1 and maybe wait for the G3 or 4 to go with my 7090