Justificus

Okay, there is definitely something wrong with this module and the NTTR map, at least on my computer. To test it I just created a new mission with nothing but the M2000 parked at Nellis in spot F65 and as soon as I hit start the FPS are 2-3. Hitting fly still keeps them there. There is nothing in the mission at all other than this plane. Anyone else able to replicate this? Is this a known issue and I just couldn't find it? Thanks for anyone able to check this. EDIT: I should add that this is an unmodded install, nothing added, not even custom skins.

I haven't flown this module in a couple of months or so and was just testing things due to losing my input setting for most of my modules when I was shocked to see that going into the cockpit of a cold parked M2000 in a mission I created gives me 2-3fps where all my other modules in the same mission give me a consistent 60fps even when flying low over downtown Vegas! I did a quick look around to see if anyone else has reported this and didn't see anything. Is this just an issue with me and my mission? I'm off to see what it is like in 1.5 and with any missions that may have come with the module for NTTR. Thanks for any feedback. EDIT: Okay, tested it in 1.5, no problems. Started my NTTR mission again and added a new M2000 to it to take off hot from the runway, no problems! Jumped in the parked one and it's 2-3fps again... I'll just have to get rid of that one... Very odd as I haven't seen this behavior before. Thanks for reading and Mods, feel free to delete this post if warranted as it is not a bug with the module. EDIT#2: I first noticed, before deleting my parked Mirage, that the ME was saying it was in position G34 (at Nellis) when in fact it was actually in F65. So I thought I figured out the problem! Wrong. Placed it in various parking spots and before hitting the fly button the FPS are as they should be, 58-60fps, but as soon as I hit fly they go to 2-3fps. Starting hot on the runway does not have this issue though. Very odd indeed! So no cold starts for this bird in this mission.

Could be right, that's one of the reasons why I don't let MS update my computer when they want to do it. I like to read about the updates and see what problems people are having before I consider updating my rigs... Way ahead of you. I have a program that detects when I make changes to my input files and then automatically backs them up to another HD. Problem is with modules I haven't flown in awhile or more specifically, haven't made any changes to the input files in awhile are all having problems... :mad: But I did figure out that I can just copy and paste once I create a new input file that is correctly associated with my controllers. Still a PITA to do but a lot easier and faster than re-doing all the settings one at a time. On a side note, what the heck is up with the M2000 on the NTTR map!?! Jumping in the cockpit of a cold parked plane gives me 2-3fps, whereas all my other modules are 60fps, even flying low over downtown Vegas! I know, subject for another thread and I'm going to head on over to that part of the forum to see what's up as I haven't been in that plane for a couple of months...

You make it sound so easy. Practice, practice, practice! :D

No, I haven't. Nothing has changed with my setup physically, that's part of what's driving me nuts with this...

Thanks for the reply, Redeye, but that is unrelated to my issue. All my DCS.exe files are already set to run as administrator. It's just that my input lua files no longer seem to be associated with my hardware, thus when I make any changes to my controller setup and save it a new lua file is created along side my old one... Very odd indeed. Not all modules seem to be affected by this so far. I've only tested a few and some are affected in 1.5 and not in 2.0 and others are affected in both versions. Really making me scratch my head...

Just encountered a weird issue. Went to fly a plane I hadn't taken up in a long time (the Hawk) and found none of my control settings were there any more. This was in the release version. I then tried the beta and it was the same. So I go into the NTTR map and those settings are also gone...:dunno: I have had all my input files backed up so I just copied them over and tried again. No setting were applied, it was like there was nothing there. Open up the joystick lua and I could see my settings were all there! So I tried again, nope, none of my settings are there in game. So I start to map them again. I exit out and look at the lua files again and see that new ones were created along side my old ones!? They have different ID numbers, for example, my input files from Nov. of last year are labeled this: {D0B306A0-A86E-11e4-8003-444553540000}. The new ones I created last night are this: {8A817250-C245-11e6-8004-444553540000}. It's like I have new controllers or something. Nothing has changed with my PC in terms of hardware, I've only had Windows update itself a few times during this time. What would cause this? It will be a major PITA to have to redo them all and it pisses me off that my backups are of no use. Anyone have an idea of what happened, and more importantly, how to prevent this from happening again? Thanks for any input (no pun intended) you can give on the matter.

LOL Fair enough. ;) Thanks for the offer. I'm able to do mods just fine, it's just I've gotten lazy in my old age and aren't able to keep up with the changes as much and have tended to de-mod my games of late just to make life a little easier. May change somewhere down the line though. Again, thanks for making/sharing these mission with the community!

Whenever it actually hits the shelves for us to purchase it will be well worth it! Looking at those screen shots makes my jaw hit the floor! Much better than I was expecting (great job guys!!!) and even though I would like it in my hands yesterday I will patiently (as much as this old fart can muster...) wait for it to get in my grubby little hands.

Thanks for the reply and consideration, Eight Ball, but don't feel you have to change what you prefer to do just to accommodate me! I'll be checking them out this weekend to see what's up.

R.I.P. S!

Eight Ball, will you be requiring mods for all your missions? I would love to give them a try but have abandoned using mods, between work, my personal life, and trying to stay on top of changes happening to the game, even though they are easy to implement (especially using JSGME) it just became more of a pain than an enjoyment to keep having to re-apply them after updates, re-installs, etc. No worries if you will, just curious. Thanks, and thanks for sharing your missions!

Really? I haven't flown the huey with door gunners in awhile... When did this change? I thought they did engage before. If kept this way, what would be the purpose of having the door gunners if they never engage?

Did you even read his post?

I think you're in the minority there. I'm looking forward to it but no way would I ever spend that much just for another map... Yes, I'm cheap! :P;)

I was taking off from Tonopah airfield, quite a small/narrow airstrip. And yes, I'm aware of the effects of what you mention but those things should not affect the rollout of a plane down the strip causing it to veer to the left sharply. Nope, didn't have those enabled. Triple checked to make sure. What I did discover was that even though no wind was setup I did have turbulence still set from my initial mission setup! Thinking it should still not be an issue because there was no wind setting for the two lowest altitudes (just like in the 1.5 map) I decided to clear its' setting and check again. Sure enough, the plane no longer drastically went to the left like before. Still not as smooth/easy a take off like 1.5 is for me but at least now it doesn't take about 20 attempts to barely get off the ground in pone piece. So, once again, user error. lol Thanks for the replies! EDIT: Well, I did some more testing and moved my Spit to Tonopah Test Range because it has a much wider runway and I was able to take off and land. It wasn't pretty but I did it in one piece. Tried 3x and was able to take off each time. Went back to 1.5.6 and it still feel a lot easier to take off and land for some reason. But especially the handling while trying to take off appears to be much less of an issue for me on 1.5.6 than it is on 2.0. Practice practice practice!

Wow, just had a weird experience while waiting for today's official 1.5.6 to release. I hadn't tried the Spit in 1.5.5, only 2.0, and found it extremely hard, even after watching some of the great vids posted here. Tried it in 1.5.5 and did what I do in 2.0 and took off with no problem whatsoever! Flew a circuit and landed. Taxied to the end of the runway, turned around and took off again without issue... Tried in 1.5.6 and was just as easy for me. I now have to go back to 2.0 and see if it's just having a day of sleep that let it all sink in or is there really something drastically different in those two maps as everything but the temp and location are pretty much the same.:unsure::confused:

Cool! Thanks for sharing that, Zeus.

Wow, I can't agree here. I haven't flown the WWII birds much at all, mostly just the P-51 and the 190 but most of my time is spent with the jets as that is my preference. Tried the Spit out and for the life of me I couldn't get that darn bird in the air. So I then tried the P-51 again (it had been many months since I had last flown her) and the 190 (same, long time no fly) and had no problems. tried the 109 and got up on the 2nd attempt (first time flying her since I bought her many moons ago...) and found it no big deal. The Spit on the other hand... that's going to take some time and effort to learn her little idiosyncrasies... But I can't agree with you that the Spit is easier to take off or land in than this current Spitfire.

:cry:

OMG! Just spotted this thread and wow, you made my year, MBot! Can't wait to check it out. Thank you very much for sharing!!!

Hmmm, not that interested in the Viggen but if it is released to morrow, I'll buy it in a heart beat! I've got some money burning a hole in my pocket and it's looking for a good home. I want something, make me happy tomorrow, Wags! ;)

Wow, this sounds really cool! I'll have to swap out your older LUA for this one and try my hand at creating a mission from it again. Keep up the great work!