Tinkickef

I agree with the OP about there not being a link to a more complete version of the changelog. However I do know that there is much more going on behind the scenes. For instance, I have in the past (and mentioned in previous threads) noticed that Normandy had substantial changes made that were not in the patch notes.. It is still a disappointment to read the changelog given and see that nothing mentioned in a lengthy download session, addresses my particular issues, even though it might. So once again, a link in the abridged changelog, to a full changelog would, in my opinion be popular. As for the rest. I think it is silly to assume that these patches are not thoroughly tested by ED before release into the badlands and I would guess that the feeling of distress and pressure by the devs responsible when it all goes pear shaped are very real, and although I also feel the disappointment deeply, and feel really pissy when the update breaks something, I think it is unhelpful to blame the devs quality control. Pretty sure they have confidence in the update before release and are more shocked than any of us when that update that gave such good results in their closed servers, suddenly cause huge bloopers when out in public. It must be like seeing a well trusted and respected colleague walk out of the building, open his raincoat and flash his genitals at passing women. That is where we beta testers come in. We witness the crime and call building security. Yes it is very frustrating and I am as pissed off as anybody else, but don't think the devs are not even more pissed. They will feel the shame and disappointment deeply as they have far more invested in this than any of us on here. They will certainly not be laughing at us. Someone suggested we have no other choice other than 2.5 OB. That is incorrect. I will just go back to 2.2 for awhile. MP players have several choices; SP 1.58, Some maps on 2.5 or on 2.2. MP on 1.58 or 2.2. You still have substantial choices. It must be remembered that the very, very vast majority of DCS users, so far as I understand it are SP users who never go near MP, I would guess far less than 10% of DCS users at any one time are on MP; so its natural to sort out SP issues first. If you want a real lesson in frustration and disappointment, try tapping out a lengthy post on a kindle fire touchscreen, it makes DCS look positively angelic.

Scattered clouds are broken at the moment in my experience. No matter the base altitude given, the lowest I ever get them is about 6000ft (Normandy 6C) maybe 8000ft on new Caucasus ( winter -2C) and above 18,000ft NTTR at 20C. Also they seem to climb with you, despite setting depth and once you have climbed above the tops, they stop generating, leaving clear skies. Impossible to fly high over scattered clouds. Full Overcast does not seem to suffer the same problems, but who wants to fly and not look at the ground? I think most of the problem is that the size of the clouds are too small, little balls of cotton wool, so you cannot have a 500ft diameter cloud 5000ft thick as it would look stupid, so they rise with you, likewise such little clouds would look stupid low down. ED are working on new clouds.

Or Num 5 if you don't want to leave the cockpit. If I know someone is taking a track ride, I usually wait for 20 seconds or so before going through the start up procedure. This gives me some time to unlock head tracking with num 5 and get the head camera in the correct position in the cockpit, before hitting esc and getting the viewer settled in. This way they miss none of the on ramp action as the jet slowly comes to life.

Must have something misconfigured somewhere. I have a ramp start mission at Batumi and my go to radio is UHF normally. Set freq for UHF Batumi ATC, (IIRC) 260.600 in radio, press my throttle thumb hat down to get UHF radio menu, F5 ATC, select Batumi and F3 for engine start clearance. OK so far. Get clearance and start up the engines while finishing up with aligning the avionics / countermeasures ect. Go back to ATC to get clearance for taxi, press F1 to ask and get nothing. Then I noticed that pressing F1 alters the tenths radio dial to 0. So frequency changes from 260.600 to 260.000. I have looked in the controls menu and nothing is bound to the radio frequencies other than my hat to select radios. Without ATC clearance my wingman just sits there. Not great when a flight of SU25s are inbound with murderous intent and its a race to get wheels up. Radio is fine on NTTR.

Apologies if it's well known info, but I have been unable to find a mention of it anywhere. I have quite a few missions on 2.2 inc. a map of NTTR where I have populated a lot of airbases and terrain with ground objects like additional structures, aircraft, trucks ect with the intention of building missions on it via save as, and save myself the trouble of repopulating each mission. Is there anyway of transferring the mission files from 2.2 to 2.5? I have tried moving the saved mission folders and individual missions across by copy / paste and nothing, 2.5 does not recognise it. If not, I will not bother building my NTTR map any further.

Timely thread. I fell for the ssd hype, having one ssd boot drive and one hybrid storage drive with DCS on it. Yesterday I swapped out the perfectly good hybrid for a new ssd storage drive in the search for optimum performance. And have not noticed the slightest bit of difference. £120 down the crapper.

Deleted mission editor folder with no luck, then renamed the saved games folder. Success. Praise the Lord and Hallelujah! Thanks for the help Newey, much appreciated. When my new drive comes...well i'm not looking forward to the cloning ect much. I expect more bleatings on here. :cry:

Thanks Newey. Did the cleanup and repair, no joy. No mission, I cannot get past the very first loading page after clicking DCS shortcut. Have deleted the root Mission Editor folder but will not be able to torrent a repair for some time as Oculus is updating and my rural internet connection will rarely get to to 2mbs. Latest crash Log printed and enclosed as zip file: dcs log.zip

Thanks for the quick response.. This is with Oculus disconnected. Any drive info in log - C=boot drive SSD. A=Hybrid storage drive. Logs.zip

As above. Not used 2.5 for a week or two and when I have come to use it again, the initial loading page that takes you to the GUI, hangs at 57% and has to be killed by task manager. This happens both in VR and on screen even when Rift headset is disconnected in an attempt to see if it was an oculus problem. Repair option has not cured it. I have been having miscellaneous problems recently from the hourglass symbol appearing regularly mid game even in 2.2 and other weird problems like windows saying I gave two PCs with the same IP address on network when only one is switched on. I have one 250gb SSD as boot drive 2 years oldand a hybrid spinning drive as storage. I am suspecting the spinning hard drive failing so have ordered a 500gb SSD for storage. ED and other folders are spread across both drives because I have not been paying enough attention to specifying file paths :doh: and I want to move all the ED files to the new drive after cloning the possibly failing hybrid. How do I accomplish this safely, without shortcuts ect becoming inop? Not super PC savvy and when finding myself in a shallow depression, don't want to pick up a spade and start digging, then finding myself down a mineshaft with no way out but a clean install of everything. Anything involving cmd lines ect has my eyes glazing over and I fall backwards off my chair.

I tried the 391.01 but it caused all sorts of problems with Rift, showing orange led, refusing to wake up, screens going black ect; so Im back on 388.59.

I am experiencing this too. Your above posts have given me the reason. For the first time I have had poor audio on startup. Side doors open, hit starter trigger, no igniter sounds and the spool up sounds like the doors are closed. Advancing from flight idle to flight rpm then sounds fine. Thanks to your posts, I realise this only occurred after I modified my mission from AI hueys takeoff from ramp, to AI hueys spawning in midair on a turn point and overflying the base.

-----running my controllers through a hub. That right there. I had issues with my warthog hotas, specifically a10 engine start by advancing the throttles from fuel cut off to idle. It would not spin up the port engine. Plugging the throttle unit into its own dedicated usb port cured it.

.......And you should see the traffic intersections in Vegas!

A common theme. I have a mission in Normandy where I have the Carl Vinson steaming off shore. I was flying the Huey with hydraulics shot out and unable to dodge withering enemy fire from various armoured units, so elected to fly out to the carrier and land there instead. So got to the carrier, got to a hover over the flight deck, transitioned right to land on the elevator, lowered the collective.....and fell through the deck into the sea. It seems that ships are not recognised as solid objects. I also had a landing ship and wanted to put a smoke effect on it for scenery purposes. The ship is not recognised as dry land and I was advised to place my smoke on the ground.

There is a setting in oculus home which says something like "allow third party games". Long time since I saw it, so cannot quote actual wording. Check that is on. DCS also has the "detect VR headset" option, but you say that is checked. Only other thing I can think of is to disable and re-enable headset in device manager to reload the drivers. I have had no problems with Rift being detected.

2.2 Normandy. Didn't know where to put this, so thought the Huey crowd will have the best knowledge base. Can't get on with 2.5 as is, so redownloaded 2.2 and am currently using that till all the lighting issues are sorted. Problem. I have a mission where I have a downed Huey at St Vaast and the crew are legging it out of there via set up waypoints, because I have a squad of Russians moving in. I pick up a heavily armed squad of infantry from Maupetus where I spawn in and start up the Huey. No problems, they jump aboard, or should I say vanish into thin air when close by as usual. Intention is to drop these troops into the LZ to guard the Huey, then I take off and search for the chopper crew, pick them up, drop them back at Maupetus, then pick up another lot of troops at Barfleur to insert where they seem to be needed. I fly out to the grounded Huey with the intention of dropping this squad into the LZ which is by now becoming hot and the bird is taking incoming fire. I F7, select disembark, select "Grunt Team 01" and they jump out the Huey. To my amazement, they leap out and run like hares in the opposite direction to the Russians! Any ideas? Troop expertise is set to excellent.

Both minor bugs. Small bug I just noticed. Flying the needles, the localiser puts you to the south of the Batumi runway and brings you in at an angle of maybe 10 degrees instead of straight in. I had visual on the runway lights and decided to fly the needles and see what happened as I had heard of Caucasus ILS problems. Description.. Night mission, HMD on, DS off. Oculus Rift. Despite coming straight in visually, using the runway lights; the localiser needle remained stubbornly a finger width to the right, so I followed it. It then suddenly centred when visually I was landing between the runway and the river, then it swung left and when centred again, I was coming in from the south but heading for the threshold at maybe 1 mile out. Not a problem if you have visual on the lights, but a bit disconcerting in very low vis. TAD bug. Description.. Despite wingman being off my wing at same alt of 18,500ft and 1 mile, his altitude readout on the TAD said he was at 17,0000ft. EDIT: DOH I just remembered I kept altimeter on QFE for Batumi, bet wingman was set at QNH.

I think (I hope) that night lighting is high priority at ED. It certainly is broken. I went back to 2.2 without problems for the interim. ED will fix it, it's just that they have so many bugs to squash at the moment. Got to feel sorry for them, must be a big disappointment to have so many negative issues from prior 2.2 users that are used to higher quality terrains. DS has badly affected night missions on 2.2 since its inception. 2.5 has just made it a lot worse. Only problems I really had on 2.2 night missions were cockpit floods, taxi lights and very little moonlight. Cockpit floods were addressed partly by hanger floodlights going full bright (groom lake) until the bird was up and taxying.

I have this with my 2 sensor setup, but only after maybe half an hour or so and after looking back to switch on the Hog lighting panel. Head height above seat base jumps 6 inches down then resets itself. Further in the mission it will do this again at random times looking forward, resetting itself about 3 seconds later. One of my sensors remains cool to the touch, while the other is noticeably warm at the rear end and I put it down to the sensor heating up and losing IR tracking. I keep thinking of moving the offending sensor to be in front of my desk fan to force cool it, but have not got around to pulling out my PC and delving around in the wires yet round the back yet.

So the 2.2 update is complete. Just had a chance to fire up the Huey and have a quick flight around the Cherbourg Peninsula. I can confirm, none of the 2.5 lighting bugs appear to have been transferred across, gamma set at 1.7, 1800GMT time, sunny and cloudless skies. The sea has that great colour again and the coastline seabed is visible under several feet of water of wonderfully clear water; Unlike the 2.5 ink. So if you were a little too trusting like me and followed the prompt to delete 2.2, you can redownload it again. It took me 9GB of torrents to do it. That includes both NTTR and Normandy, plus all my aircraft. The rest was transferred across from 2.5. It also looks like all my control binds and settings were also restablished, side doors opened and closed, force trim ect all worked as before. Still have the system stutters in VR, that appeared in the last 2.2 update, but with windows, oculus, nvidia and DCS all updating themselves, windows and oculus without being given the choice; who knows which actually broke it. Of course the best course of action would be to be a little more cynical than I, and don't delete your 2.2 folder in the first place! I'm an idiot, I was taken in by all the pretty promo vids. What else can I say.

This used to be a minor problem in 2.2 and specifically Normandy. You can see the rotor head turn and the outer portion of the blade, but not the inner. I suspect the blades are divided into portions due to different rotational speeds and the inner portions are not getting picked up as shadows. NTTR 2.2 did not have this problem despite same settings. I usually have shadows low. I should have mentioned it before, but was never that bothered. I do enough moaning :) OP can you be a little more specific about which map and settings ect, so the devs can make a note and try replicate the problem when it comes to the top of the list? It is a minor problem as you say, but they do read these posts and prioritise fixes. This is minor and will be low priority, but may be fixed as part of a bigger overhaul. The more info the better.

Cockpit light bug has been around since deferred shading was introduced to DCS 2.#. So its been around a long time, and most of us night owls have found workarounds. I could probably start the Hog blindfold now. :smilewink: More serious bugs have come with 2.5 that affect the view out the window. ED are no doubt busting a gut to repair the problems, but a lot of them will be very complex and deep seated, so don't expect it done quickly.

Portsmouth, or a small town in the vicinity of where Portsmouth should be was added maybe a couple of months ago, along with a few other villages and smallholdings. No Southampton or the rest though.

Agreed that Normandy is getting a lot of quiet attention. The coastline in 2.2 is pretty good with clear water through which the sea bed can be seen through several feet of water. Even England is getting a little love. A few more towns and villages than previously. I see quite a lot of stuff not seen before on Normandy, Ugra are obviously still hard at work on it and ED are slipping these improvements in under the radar. Still have not found any concrete runways though. It would be nice to have the option to lay concrete runways and roads in mission editor. Normandy is really in need for detailed airbases of the quality of NTTR where appropriate long standing bases existed. A big improvement that does not seem to be mentioned is the very improved framerates over sizeable towns and cities. I have seen the new stone water towers everywhere, but no new bridges, still the old steel spans.