mkiii

Just so you know - Blender3d from Blender.org, (or Steam), which in case you live under a rock, is free. Loads these DDS files - you can just drag them onto a cube object to view them as a Colour map, or attach them as a normal map to see the result if you delve a little deeper. THey can only be saved as a different format however - such as TGA. A word to the wise though, you might be wasting your time, and all you might be saving is some disk space. I wouldn't use jpg files for normal maps either. Also, just because a 32bit file is loaded, it does not necessarily mean it will be store in memory at that bit-depth. Finally - I'm not sure where this notion that 32bit is not a power of 2. Count along 2, 4, 8, 16, 32, 64, 128, ...:music_whistling:

I still find it hard to believe that a fighter sized aircraft such as an F-16 or A-10 can not fly in close formation with an identical aircraft without being tossed all over the sky if you fly anywhere near it's wake. I have seen a fair few 4 ship take-offs of Jaguar, Buccaneer and Tornado, and never saw any sign of the rear pair(s) jiggling around in the wake of the lead-ships. And as for F-104s I don't recall any more than 1 or 2 ships on those, but they don't hang around on take-off or have much in the way of wings to be affected anyway bloody missiles ;) The link to the USAF video above is talking about flying small light trainers such as the T-38 through the wake of heavies, and specifically at low approach speeds. - that I understand. If it is a realistic representation, then the red arrows must have magical powers. Their smoke is only affected by the turbulence of their own engines. Maybe it's just that British aircraft are better? :music_whistling:

I don't agree that something that is not as detailed as in real life should be scrapped before it is even attempted. I think all that reasonably well informed users, who read these forums, have a fair understanding that some things can not be included, or at least have functionality that might be classified, but there is no real reason why some of those systems such as IFF can not be faked or simplified to at least have some functionality. As long as the documentation makes it clear that this is the case, then who can complain. It also isn't as if every line of code is written from scratch in a complex application - they do have libraries and reusable code.

I might be misunderstanding the issue, but if I have edited a mission, and don't want it to be saved amongst all the other missions in my Saved Games folder as you are describing, I create a new folder in explorer so I would then look in "My missions\Campaigns" and see a list of folders that I have created - one for each aircraft if necessary. I admit, that it would be a tiny bit easier if the save dialog in the ME allowed you to create folders though.

Interesting. Unfortunately, I am not using Firefox, and the issue sometimes remains, even with the new forum. Last post it made the extra spaces. This one it did not. Odd. EDIT: So I made a new reply on a different thread and the problem returns. Ironically, this post is formatted correctly.

Look in Saved Games\DCS\MissionEditor\settings.lua Near the top are "missionPath" and further down settings for the recent files.

I guess it isn't getting fixed any time soon then.

Good. I thought I was going blind!

While there are workarounds - such as assigning all keystrokes to each MFD via script hacking, I really don't see any reason why this is not done by default - I don't want any greyed out buttons on ANY controller - especially when it means you are not even able to assign a Shifted command to anything. For example, I use the SYM, CON GAIN & BRT shifted for easy up/down Waypoint, Heading & Course bug ands so on.

This method did it for me.

And while you are at it guys - add an option to get rid of the tiny repeating crackling effect on all canopies - or update the texture from it's present form. Canopies without this "effect" look much better. It always looks bad when it tiles, and that is magnified many times when you see it in the side monitor of a 3 screen setup, flying in the golden hour with sunlight streaming in the side.

"I DON'T KNOW WHAT I WANT, BUT I WANT IT NOW!" :)

If my memory serves, trees did not used to have collision. Just a guess, but the SU25 has not had a lot of effort spent on it for a long time, so I'm guessing that perhaps the missions predate the newer trees with collision detection.

Unless the F-16 has some magic, it should have a relatively narrow beam perpendicular to the axis of the aircraft. As mentioned above, when you bank - that distance increases. Bank past a certain point on flat terrain, and you no longer get a reading. What you have to look out for is low flying in a hilly area. Take a valley for example, your rad-alt might say 500' if you are above the valley floor, but the hill to one side is only 100' from your wing-tip. If you then bank level with the slope, your rad-alt should show that lower height, not the height to the valley floor. If you bank the other way, towards the slope, the rad-alt will show more than the original 500', even though the ground directly below you is only 100' away at best. 'taint rocket science.

Absolutely. I can now steer onto a taxyway [sic] without the aircraft falling over.

Bump: Problem still exists as of today. EDIT: Belay that. I discovered that the Escape Menu command keystroke was missing! Go figure. It's not something I even thought was configurable. This does not explain why it worked for a while then, in the same session, stopped working.

I'm using Open-Beta so may differ in setup, but the Uncage Switch ©, and the Enable Switch (ENTER) do seem to be doing the same thing here too. I think the Uncage button may operating incorrectly, it's hard to tell, since it seems not to function unless a target is in view!?. The Enable switch seems to function as it should - setting Bore/Slave modes. It isn't working asw it does in "other sims" - but they could be wrong. TBH, I'm avoiding the F-16 right now - it is too incomplete, and the ESC menu has stopped working with it for me.

I have a similar problem in that the ESC menu does not work in the F-16. This seems Not to be related to any button sticking - I previously thought it was a sticky pinky switch acting as a modifier. However, I can (at the moment at least) without fail make the ESC menu come back again by jumping to another aircraft type. The ESC menu then works again. To test this I used the F-16 free flight mission using the A10As present to jump to. I use the paddle switch as a modifier on myTM WH stick on many aircraft - it is not sticking - and it works on all but the f16. It seems intermittant though. This morning it worked OK as I was modifiying stick & throttle assignments. I have not changed any key assignments - I rarely if ever do that for any aircraft. ESC is definitely not one that is reassigned.

I would also like to add to this, and option to turn off the fake looking cracking/scratching effect used on almost all modules - which is a really obviously repeating very low res normal map, and has not been updated at all since day one, which looks absolutely terrible if you use multi monitor setups. It is just about bearable on a single screen, but the option to not have to bear it (unless it is improved) would be nice. I guess that it is low priority, but just look how other sims do it guys - if you have to keep it, at least make it look less tiled & use a higher res texture.

Canopy bind. is actually missing. Thank god for that - I thought I was going blind ;)

Thanks for the info chap. I guessed that it must be something a bit more recent than the 90s. As I said before, I understand that the later models may well be very different to the old (well they were new at the time) 16s I handled back in the 80s Unless I imagined it all... There was a lot of beer in Germany that had to be drunk back then after all. PS can ANYONE tell me why every post I make on this forum adds double spaces after a new line & adds a huge space at the end like this? vvvvvvvvvv

Just a note that the fans, compressors & turbines aren't really producing any real torque. They would only do so if there was a significant shaft output like a turboprop or I suppose if the engine or its mounings were significantly offset. I have found the F16 to be extremely tippy. I can easily scrape my nose or a wintip, or even turn turtle just by turning too fast while taxying.

Perhaps because you are not moving the stick position with trim in the F-16, afaik, but in other fighters stick trims will physically reposition the stick to hold a position - so you don't have to hold it in that position.

How do you mean "doesnt recognise". What is not being recognised? Keystrokes? Numbers? Functions? Numlock on or off?

If you watched the track Frumpy provided, you would have seen that his flight was at mostly approach speed and gear down, apart from an initial period of about 560kts. I'm not sure if it is the track glitching or what actually was flown, but the only uncommanded yawing I saw was due to flying at, and below stall speed. The stall followed by a nosedive into an apartment block is probably something you should expect. That being said - the current iteration of this aircraft (maybe others too - I havent checked), is VERY prone to sudden departure when picking up turbulence from another aircraft. Even the Wingman F-16 in the Caucuses Free Flight Insta-mission. It's like getting behind a 747 wingtip wortex in a hang glider. Tht's not happening here though, the other aircraft are miles away at different altitudes.