Pheonix0869

Also Checking in! Wow! Fantastic Job! I too ran into some taxi issues in Mission 9, however after checking the forums, I loaded a arbitrary mission, quit, and then loaded the campaign and the problem was fixed. Besides this (very minor) bug, the missions worked flawlessly. Sometimes things happened in quick procession and the coms were alive with pertinent information that I did not always catch in time. Which is ok, this is how things happen, and if anything it taught me to pay more attention and/or improvise based on educated guess work! I found I typically read the briefing before the mission and then the frag order as the INS aligned. This allowed for very little downtime, that can negatively effect my limited attention span. I very much enjoyed that the radios had to be used appropriately, as well as the Bingo and IFF being briefed! This adds a level of immersion that pulls one into the conflict. It also prepares novice players for servers that utilize Simple Radio Standalone. ... I mean the IFF not so much, but still very cool. I really appreciated the briefings being in the knee-board. For us VR pilots it is an invaluable resource that can be very quickly accessed! [spoiler Alert] I must unfortunately disclose that I have never completed a campaign before. I just honestly loose interest and most stories are... "eh". The narrative of this campaign is what kept me coming back, and I knocked out the whole thing in a week (last week of winter break, and all). I really applaud a character development of this quality in a flight sim! I find myself wondering... no. Hoping, that Col. Raunier is alive, and meets up with his two American tadpoles in Nevada! It should also be noted that I've tried very hard in the past to AAR with the M2K, to no avail. When Raunier was watching I got it on the second approach and have been consistently getting better ever since. I really felt like I was going to let this guy down. (That would be a cool fail state... "I thought I saw promise in you..." [Raunier]) Anyway, in closing I thought this was brilliantly constructed and full of the human aspect of military aviation! I'm glad to have read that you will be focusing on better A/A engagements moving forwards, but what makes these missions good is FEELING like a pilot by utilizing every system of the aircraft, and not so much the action! Looking forward to your other work!

Hey guys, figured I would add me two cents (which would also bump this thread up to the most recent...) Maybe there is another squadron that we contact directly, who fly 190's and 109's? I think there a German squad on IL2-BOS that play DCS!

Guys with merging geometry try turning off Rift's ASW by hitting ctrl-numpad 1... I too am noticing some frame drops with Rift, probably due to the fidelity of the prop. Without VR there is no noticeable frame rate issue. Hang in there guys its day 1! There are many more improved spit days to come!

I thought they were banned by the U.N. after the Theta Protocol incident...

So, the export is a little confusing... Here's what I can do, maybe someone else can provide further assistance!? I'll upload my export and the TACVIEW export... these files belong in your DRIVE:\Users\USER NAME\Saved Games\DCS\Scripts... Export.lua TacviewExportDCS.lua

A few of us fly Sunday afternoons in NTTR, hopefully Normandy soon... with the Mustang, usually around 20:00 zulu (GMT)... It is very casual, which makes it a great place to experiment with different tactics and such... you can PM with your E-mail and I'll pass it along to our group admin and he'll get in touch with you! Good luck on your search!

In the replay i just watched the engine started? There are a few things I did notice, that I do differently. Usually, I hold down the primer for 4 seconds... ish, also you would want to open the throttle a crack. Try using the auto-start feature I think its win key - home, this should allow you to see whats going on... If there is still an issue maybe repair DCS, I'm sure there's a thread on that, but basically from windows you want to hit win key - r, type in cmd and hit enter. At this point you are in the command prompt. type cd and the path to you dcs install including /bin. type in DCS_updater.exe repair, and this will prompt the exe to check your files against those on ED's server and correct any errors. cheers.

It seems like the S530 needs to be seen by both eyes in VR in order to appear, thus "popping" in/out when looking left or right. This might be an ED bug, but I'm not sure.

Its my understanding that Belsimtek set the price, but it is however steam that is handling exchange rates and they often don't fluctuate as they should. I would advise just not using Steam for DCS, as the standalone experience allows you more beta modules, quicker updates, and no drawbacks... I'm actually interested to know what the price for the module is in the DCS store for you? Is it different than Steam? Edit: Just kinda read the part about not suggesting standalone, sorry m8, only solution I could think of...

As far as having different server lists, it is entirely possible that you are running two different versions of DCS. Not just the 1.5, 1.5 Open beta, and 2.0, but all the numbers after that. In the past being outdated wasn't an issue, but ED has updated some network code recently, meaning that 1.54 cannot connect with a 1.55 server. To make sure you have current versions check out this site (http://updates.digitalcombatsimulator.com/) and (I believe,) in the lower right hand corner of your main menu you'll see the version you are running. To "force" an update, open command prompt by simultaneously pressing Win key + r, type in "cmd" and hit enter. Then type "cd" space "your install path of DCS_updater.exe" space "update" and hit enter. It should look like this: c:\Users"name">cd C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe update Hope this rambling helps!

two weeks...

For me (atleast) I found it was the introduction of the ASW as opposed to ATW... bascially this is occulus' new way of trying to reduce system reqs and improve frames, but i find in games with cockpits and/or quickly moving objects the ASW actually works to a disadvantage... You can test this by booting up dcs and then hit Ctrl - NumPad 1 (while NUMLOCK is ON). That will turn the ASW off and the ATW on... in order to turn the ASW back on you can use Ctrl - NumPad 4... cheers, and some more reading if you're interested... https://developer.oculus.com/blog/asynchronous-spacewarp/

Okay, so in case anyone reads this... I think I have narrowed down the culprit! It seems when I disable ASW by using the Ctrl-Num 1 (with Num Lock ON) I no longer have an issue. This seems to be only effecting DCS atm, but it could be a hardware issue as I am running a lower end cpu... anyway thought I would keep this updated!

I noticed (in the F-5, UH-1, and Gazelle... so far) that there seems to be inconsistency when displaying textures... almost as if they are being sliced and offset. This is usually happening where a shadow meets a texture (for a quick example, you can load up the f-5e at night and just turn on the flashlight.) It also seems to occur when the the cockpit texture meets the ground... I will try some other things as well and maybe a log file will help, so here's a log file... dcs log.txt

Once DCS starts up I usually hit Ctrl-Enter in order to make DCS full-screen and then your cursor won't hit the task bar either...

Fixed for me in 1.55 open beta!

Thanks for the quick response, and no worries. Figured you might want a heads up if it was an unexpected glitch. Keep up the great work!

Seems I am unable to access the Gazelle in 1.5 open beta. Whenever in the ME, or any other mission is selected, after the briefing I am given an F-10 map with the AI (presumably) controlling the chopper...

Left ctrl+F11 (default) puts you into a free cam relative to your last camera position. i.e. If you're in first person the free cam will spawn in the cockpit, or if you hit F2 to see your wingman and then ctrl+F11 the camera will spawn there. Also mouse wheel increases and decreases the velocity of the camera, so you can "fly" the camera.

I waited until the "open mic" message from the crash finished before taxing. I don't think you get clearance before that, so I feel like your wing man crashed into a car that was scripted to do something else (i.e. respond to the crash or block the runway for emergency vehicles.)

I find that immediately saving the replay, then returning to the main menu before playing the track helps... then I replay the track WITHOUT time acceleration or changing the views, and save that replay... then with the new track I find I have much less trouble, but changing the view often or quickly, and time acceleration seem to degrade the probability of a successful replay. There are also times when a track just can't be saved... I also find success rate varies with air frame. If there is dynamic weather forget it!

I think one of the existing problems with many of the missions online is that they lack a fail state. It would be nice to have advancing opfor as well as predetermined targets. I had an idea consisting of a unit travelling from the red airbase to the blue airbase. The unit would carry a dirty bomb, or whatever fits the fictional bill, and would have to be hunted and identified by low and slow choppers, who would in turn have to talk on fast movers. The position of the threat car would be known to the opposition allowing them to fly cap and intercept search choppers (gazelle cap!) Add some static AA and this mission would bottleneck the action and allow for meaningful teamwork. I'm sure the idea needs some refinement and obviously sides could take turns sending the car. Sorry for any misspellings, Im using a touchpad.

Yeah after the fuel pump you should release the rotor brake (big red handle) then wait 15 sec then engage starter, wait until rpm (i think) reaches ~2100 then increase throttle until the blades start to spin... wait some more, until both needle are even and then slowly increase throttle until full. Boom.

I'm surprised this hasn't been done yet...

jasonstory, try closing simshaker from the tray in the lower left of your desktop, then reload the "disable simshaker" file from JSGME by un-loading and then reloading it... this should solve your problem as it did for me today. When sim shaker is running I assume it adds the kneeboard file if DCS starts and doesn't have the modded file.