Jarhead0331

Yeah...some of us aren't as I-Ching, one with our spirit, as others...:music_whistling:

I dunno...I'm getting to the point that I really don't want to hear anything from the development team until release is really imminent. I rather delude myself into thinking that release could come any day, then see a status update that leads me to believe its not for weeks to come.

Comments like this are appreciated, but they break my heart. They make release seem so far off...:cry:

^Hates capitalism, but just...can't...wait...to pretend to be a pilot of one of the fighter jets that defended the oppressive tyrannical blood and money thirsty regime for almost thirty years. :pilotfly:

My personal problem with the hype train is that once I’m on it, there is no getting off and while I’m on it, I lose most of my motivation or incentive to fly anything else. I don’t want to continue learning the Hornet, for instance, because I feel like the tomcat is just around the next corner. So, I end up grounded, not flying anything seriously until the next hot module is released. It’s like having sex with I gorilla, I guess...you can’t stop it until it wants you to. I know this is my own problem, and place no blame for it anyplace else.

Sweet baby Jesus, this module looks awesome.

I think I got it...looks like I ran the update that hit this morning before I tried out my VAICOM which I set-up last night. The update reset the .lua files.

I have VAICOM PRO 2.5.3 running in debug mode and everything looks good. VA recognizes my voice commands and my PTT buttons on HOTAS and keyboard seem to be working. However, in game, DCS is not recognizing anything and it is not working. I have the Steam version of VA and the non-steam version of DCS open beta. Both are installed to my D: I did the manual export of lua files per the manual...what am I possibly missing? Stupid question...do the radios in game have to be on and set to proper frequency to work? I notice in the F-18, even before I installed VA and VAICOM plug-in, I had issues communicating with ATC and at times wingmen. In other words, If I'm cold and dark on the ramp and try to communicate with the ground crew, or ATC, is it not going to work becaue I'm not powered up and configured yet? I've tried to test this by starting from the ramp, the runway and in the air and it makes no difference.

Thanks for this. I hadn't thought of using the hat for mouse clicking. That's an interesting idea. After some limited experimentation, the mouse seemed much better for cursor control than using the VR headset look option, but your system is at least worth a try. I see most people getting all different kinds of trackballs or touchpads and mounting them in all sorts of strange places...on throttles, on desktops, strapped to the knee or other body parts and appendages, etc. It all seems like too much effort to me. lol

As the title says, I’m really fighting to get comfortable flying this sim in VR. My biggest hurdles seem to be finding the right positioning of my seat (ie distance from controls, height of chair, etc.) to maximize my ability to comfortably look around the cockpit, reading displays, labels, screens, etc. and finding a system to interact with the cockpit that it comfortable, reasonably fast and practical. So far, I use a combination of using the mouse and VR headset view control to interact with the clickable cockpit, but this is still overly cumbersome and clicking on knobs, buttons and switches is more difficult than it feels it should be. Of course, I’ve mapped most of the critical controls to HOTAS, etc. but sometimes I just naturally prefer to interact with the cockpit. When I get frustrated, I find myself either going back to trackIR or playing VTOL VR where I can actually interact with the cockpit controls with the motion wands of my Vive (fantastic sim, by the way and vr experience). Anyway, any suggestions or tips to get over these humps, or are they just a byproduct of the limitations inherent in the current generation of vr headsets?

Thank you. Is there any reason to wait for it, as opposed to using the skatezilla utility?

Is there going to be a separate download for the 2.5.0 beta? I had a really nightmare of an experience last night and had to delete my 1.5 beta and 2.2 open alpha installs. So I’ve started from scratch and the only download I can find is for the stable branch of 1.5.8. I’d hate to have to now wait until next week to try out 2.5.0 when the beta ends. Thanks all.

It would be a really nice birthday surprise to get this tomorrow. It is, after all, the 242nd birthday of the Marine Corps. Semper Fi, I know what I'm wishing for.

Man...that would be an awesome way to learn and a heck of a lot of fun too! Thanks for all the tips so far. By way of an update, I just tried out the Huey in 1.5.3 again and I was able to take off, manage a circuit around the airport and land again safely on the runway. It wasn't pretty, but I did it and caused no damage to the airframe. I need a lot of practice, but I didn't feel anything was "off". The issue I'm having appears to be related solely to the Gazelle in the alpha.

I put the control overlay up and everything appears to be functioning as intended. Still, whenever I apply enough collective to get off of the ground, the helo begins spinning uncontrollably and my efforts to correct it only seem to make it worse. I'll try to record a huey track per 8 Ball's suggestion.

I have my RZ axis on the stick set to rudder, and as I mention in the OP, I apply it to try to counteract the spin. It doesn't help.

OK...so I know helicopters are very difficult to fly, but really, it CAN'T possibly be this hard! I can barely get them off the ground and its extremely frustrating to go through the start procedure only to crash and burn before even being able to break 10 feet. I suspect the problem is one with my control settings. I have an X55 Rhino system. I have the throttle set for collective and the stick set for cyclic pitch and control. What else is there that could be screwy? Trim settings? What is causing my helicopter to totally spin out of control? I've tried applying collectively slowly and quickly and none of it makes much difference. I try applying rudder to counteract the turn, but nothing works. Fixed wing aircraft function fine more or less, so I know its not a hardware problem. What am I doing wrong? The problem is extremely severe with the Gazelle and pretty bad with the Huey too. Last time I tried, I was able to get the MI-8 off the ground and fly around, but I was pretty much like a barely controlled brick. Any help or advice would be greatly appreciated. Thanks.

I have no objection if the upgrade installation checks for a legal version of BS1 on my harddrive. What I object to is the fact that the check doesn't work. I have a legal copy of BS1 on my harddrive and the upgrade installer REFUSES to identify it. I have bought BS1 four (4) times. First the Russian version when it was released in beta. Then the English version when it was released for download. Then a boxed version when I saw it on the shelf in Bestbuy and finally on Steam when I saw it on sale. To not be able to install the upgrade version which I purchased for $19.99 is unacceptable. ED needs to fix this...

I am very dismayed that there does not seem to be an official position by ED on this problem, or any effort to resolve it. It is clearly a problem experienced by a number of customers. There are dozens of threads on the topic and very little input or feedback on how to solve it or what to do in order to avoid it.

Nope...tried that too. Same problem. DCS World refuses to detect my install of BS1. Now I noticed that if I go into the module manager and check out the installed modules tab, KA 50 is there. HOWEVER, when I click on the serial number button, it says "No Key." Unfortunately, I am unable to manually type it into the box. Still, I'm not sure why it is not there. BS1 is activated and it runs fine when I launch it from its own shortcut.

I've done this and I'm still having the same problem...see below: http://forums.eagle.ru/showthread.php?t=105214

I don't have any drop down boxes in the module manager, so I'm not really sure what you are talking about. In my module manager, each module is listed separately, and I click on the install button to the right of the one that says BS2 - UPGRADE. I'm pretty sure I'm doing that much right...then when the install begins to run, I get the pop-up telling me I need to have BS1 installed and activated before I can install BS2.

I've conducted several searches on the issue of upgrading BS1 to BS2 and although I have found several threads regarding the problem, I am yet to find one that concisely explains how to do it, or one where the OP was able to successfully solve the problem and get the install working. I'm not saying such a thread doesn't exist, but I just want you all to know that I looked, before you yell. Anyway, so I have DCS World installed and updated. I have the modules for Combined Arms, A-10 and UH-1 Huey all installed and updated, as well. However, I simply CANNOT get BS2 to get installed. How the hell do you do it, step-by-step? I have BS1 installed on my system and activated. It does not run through DCS World, I use a separate short cut for it, and it is updated to the latest version and runs fine. However, when I try to install the BS2 upgrade through the DCS World module manager, I get a pop-up telling me that BS1 must be installed and activated first. Why is the module manager not detecting the BS1 install? Does the BS1 install have to be installed a specific folder? If so, which one? What else could the problem be? Please help, this is very frustrating. Thanks in advance. S/F

So what exactly does that say about the Ka50? :( Its a platform that was developed at a time when there was a lack of funding and a lack of interest in its concept. It was developed by a country behind the times in avionics technology and is intended for use in "low threat" environments... Sounds like a lame duck to me. Don't get me wrong, I love flying the Black Shark in the simulator, but it seems like a pretty weak platform for 21st century armed conflict based upon your statements...:joystick:

Well, at night, you can't use the helmet sights because you have the NVGs equipped! :cry: For the sake of this conversation, I don't think that is a fair comparison. The AH-1 was delivered to the US Army in what? 1967? The Ka50 was designed in the 1980s and first delivered to the Russian military in '95? Clearly night vision technology had improved by leaps and bounds in the approximate 20 year gap in development cycle. I don't think there is really an argument here to be had...I just think its a Russian design philosophy that I personally don't see the logic behind. But thats just me.