Oban

More akin to them taking the ignition keys !! :megalol: Don't get me wrong, they broke my modules too, well, the modules are not broken, the addon product is still the same one I was using 7 days ago, without any issues, and the re activation bollocks isn't the best thing on start up each time either. But I'm also open minded that this base product is still not the fully released version. Do you recall Wags saying after initial release they hoped to have 2.5 stable to release as a public build in 2 weeks?? :lol: That was the kiss of death right away!!

You have also missed the main point, the initial product, that is the map, along with 2 flyable aircraft are FREE.. which makes it a free product does it not? If you want to fly certain aircraft on the free map, then yes, you have to purchase those, I'm not talking about purchasing additional aircraft here, 2.5 even in it's current state is a free product. 1.58 was a free product 2.0 was a free product.. If someone gave you a free Subaru imprezza, without all the trimmings, but you bought and added all the spoilers and alloys etc and fine tuned it, at your own cost, regardless of what you did,the base product was still free.

Nope, the map is free, as are 2 aircraft. You don't buy modules without needing the base product first. :smilewink: that's like buying a spare wheel for a car you don't own !! All the modules are optional, the base terrain didn't cost you a single penny.

This right here.. is complete nonsense, it does work, sure this latest "update" seems to have a massive glitch with the Nevada map, but to state 2.5 simply does not work, is hyperbole at its finest. Initial release of 2.5 on my home rig on a crappy 970 and 16GB RAM with everything apart from traffic maxed out was a treat, and it was even better on this laptop. The last update has caused more issues than it fixed in my opinion, but it still works, looks great, lots of room for improvement too, sounds like taking a break from DCS would do you the power of good, and those of us who enjoy this release, despite the botch up with Nevada, can fly in the skies, till our hearts are content .. It's not rocket science, if something bugs you to such an extent, don't do it, stop playing it, uninstall it.. find something that doesn't vex you into making hyperbolic statements.

Seeing as it's a beta release, we, the general public are also testers, and everything that can be picked up is being picked up, all very well saying things should have been picked up internally, yes, for a general release, not for alpha's or betas. We all downloaded the current build knowing it wasn't the final version, for sure this latest update trashed Nevada, and that's unforgivable, as that is a product that people purchased in good faith, Caucus map was a free product... free, something that's lost on many people, unhappy at a product they got for nothing.. :music_whistling:

Works a treat Looks better, now all they need to do is fix all the things the last update broke!!

My torrent was 10GB, it all depends on the number of modules you have I believe. My modules are: Nevada Normandy F5E Spitfire FC3 WW2 assets pack Black Shark 2

Mambero75, I never said it wasn't any good, graphics wise it's the best release to date, what I said was that reading all the negative comments with regards to the terrains "early release/pre alpha" hasn't been met with open arms. However... since the last upgrade, it's broken complete modules, and is leaving blokes pulling their hair out with frustration, myself included, they wiped out the entire 3d objects within NTTR.. So back to the F/A18, I'd much rather be able to fly a stable build when it's available, than an early release that has a very good chance of being trashed, due to terrain updates.

Ticket created with regards to rebinding, thank you.

Yep, seeing lots of people suffering from the same issue, the hotfix didn't fix it for me.

The latest patch for me has disabled my steam version of FC3, prior to this update, I was able to use it and all the associated missions, now it's all gone.. Seriously guys?? Very disappointed, none of the VSN addons work now either due to FCS being disabled, especially after it too 28 hours to download the update, only to have it render all addons useless... Uninstalling is not an option due to limited internet speeds. dcs.rar

Okay guys and gals, I'm thrashing about with the VSN Tornado GR4, and notice that on ejection, post mission shutdown, the pilots are Russian fighter pilots, how would I go about changing these to American USAF/USN pilots?

It'll be done when it's done, considering a substantial amount of negativity of the much vaunted release of 2.5 and its inherent problems, as an alpha release, I'm sure ED would much rather this flagship product would be greeted with more praise than 2.5 was, and take their time and making sure it's released as an acceptable working "early release". I'd much rather they spent a little bit more time fine tuning this anticipated release, than to read scores of threads of " negative responses", similar to 2.5. Early release = far from final product, lots of bugs, and a heavy Works In Progress" state. A LOT of the goodies will be complimentary with the new shaders in 2.5, you can please some of the people some of the time, you cannot please all of the people, all of the time.

Download the VSN Tornado GR4 pack, and use the A10 cockpit, you can still thrash through the Caucus valleys, at 400 knots, with the nearest thing to an actual 100% working module. I've made quite a few liveries for Op. Granby, and Op Telic for the VSN addon.

So you're suggesting that DCS should not have released a product due to market prices of another product, that may or may not be needed to run the sim? There are PLENTY of people, myself included, who don't run 2.5 on 10 series graphics cards, who also don't have any of the issues the OP has. There are plenty of comparisons, and tweaks posted that could easily have read through as well to optimise their game for better results. The harsh facts are that if you want to run ANY of the latest sims and games in their FULL glory, you're going to need the hardware to achieve the best results. Minimum specs are a guidance, not an absolute.

The M551 Sheridan isn't British, and would have no place in an RAF equipment addon.

I placed the shapes in the VSN_Tornado addon, in the shapes folder there and that's what worked for me, great models, a million times better than default.

Disregard, got it sussed!

A quick question, where do we place the shapes in the shapes folder? replace the originals?

Define fine?? Everything on max? with a constant 60 FPS ?

That's exactly what I'm looking for!! thanks mate Nice looking Tonka's too

Would you consider sharing these models? :D So to correct this error, the "weapons" part needs to be shit canned, I'm heading back overseas tomorrow night, back to the grind, will try this out shortly, as packing my shit up, and thinking how to get my TM16000 into my cabin bag hahahaha

I'm pulling my hair out here mate, tried the synatx you've written, and neither colours are showing, the default one is !! Arggghhhhhhh LOL. If I delete the weapons line from the description, it selects the tornado-wpns.bmp from the temp folder If I leave the line it, it selects the default tornado-wpns.bmp I need to see the actual dcs description.lua for their Tornado GR4 to see if there's a typo in my lua.

Thanks mate, will give it a bash, so far it's not doing what it should, the texture from the Temp Folder is overwriting it, might have a typo going on somewhere that's stopping this from working. Appreciate the help though.

How would I go about using 2-3 different variations of that "weapons" texture, rather than keep replacing the one in the temp folder, depending on the colour schemes I'm flying? EG. If I added the pink textures and called them "tornado-wpns-1.bmp" and had this line in their description.luas, would they only use the one from the temp folder? Same with the all grey version, but with a different number syntax? I keep having to swap them out to take screenshots etc.