Jump to content

SamVimes

Members
  • Content Count

    15
  • Joined

  • Last visited

Everything posted by SamVimes

  1. Samson, Thank you for what was obviously a lot of hard work I have enjoyed this campaign a lot. Just to let you know there is still a couple of problems I have found. Mission 6 still never gets it's fire started but I just moved all those files to a backup and went on to the next mission. I have now found that the second last mission, "Weird mission" I land and park but nothing happens after Falce 3 lands and despawns. Falce 1 had already crashed into the truck that pulls up to my right. I can do the same trick in order to finish the campaign but I'd really like to fly
  2. Fantastic campaign, really enjoying it. Just thought I'd let you know about a couple of little bugs I have found recently. On the way to target the flight only wants to do approximately 185 mph which seems way too slow. In a couple of the later missions, 17 and 18 from memory, I have found some problems. In 17 we are attacking some artillery and we get attacked by 109's after our first run. So we clear them out and instead of going back to attacking the artillery or heading home due to lack of ammo, my flight just do lap after lap around the target not attacking nor hea
  3. Yes, I have fought many in my P-51 career along with quite a few 262's.
  4. Thought I remember... ruffle, ruffle, ruffle... Ah Here it is. Have you tried Settings/ Key mapping/ Engine controls. Third from the bottom, "Interconnect throttle and prop controls"? Default keystroke is LShft + I HTH, Craig
  5. Thanks for this great little trick I'm going to try it out. I bound it and briefly tried it on a Spitfire 9 on the ground. Looks promising. Hate, Hate Hate, taxiing that damn Spitfire. I can do it, but only just and only most of the time. One odd thing I just found. I added this axis but didn't take away the "/" for full brakes for both wheels. Now if i hold "/" for more than half a second or so, the brakes stay locked on full. At least according the pressure gauge in bottom left of the instrument panel and I don't hear the release of air either. A quick twist of the grip will rele
  6. Sorry for the late reply. Do you mean the _gen.log file because if you do I cannot find that file. I have other files starting with an underscore and having a log extension but I cannot find that particular file. Well that's strange. Just had another go at an airspawn in that same Dora career and it worked properly. No problem. Still no _gen.log file however. Maybe I was holding my tongue correctly this time.😁 I don't know. Thanks again, Craig
  7. I now have, since flying again in the Dora, a _gen.mission file in the \data\mission folder which I have attached. Still no _gen.log file but there is an _mgen.log if that helps at all? I have now found out that I spawn in the correct place on the map, the middle of a forest 10 kilometers from point 2, but at 0 altitude. Let me know if I can help at all. TIA Craig _gen.zip
  8. Neither of those files can be found in those places immediately after attempting to fly a Dora mission. They were there before attempting to fly this mission. I had been flying other aircraft and then read your message. I found those files and guessed that I should fly a Dora mission before sending them. Went back after this (mission behaved exactly as described above) and neither of them were there. There are other files starting with an underscore visible in those folders. TIA Craig
  9. G'day All, Just found a bug I haven't seen before the latest update. In career mode when trying to air spawn a new mission in the 190 Dora it will spawn flying directly into a stand of trees. The plane seems to be just a meter or so above the ground and appears to be just a few meters from a forest. Subsequently a crash into said stand of trees happens. Have tried out quite a few other planes and they don't seem to have this problem. The current date of my career is 21/02/1945, the squadron is III./JG54 and the airfield is Babenausen if that helps anyone. Not a big deal as I can su
  10. Thanks for the clarification Gordon that helps. No apology necessary. As far as I'm aware Virpil have removed the sensor you mentioned in this latest revision which may cause some slight problems flying twins but I do that so little it shouldn't bother me. Yeah I have enough trouble spotting as it is, VR is definitely not on my radar. Thanks again mate.
  11. Excellent so, just to be clear in my addled brain, remove the binding for "Engine Throttle Control" and just bind #1 and #2 and that will work for both singles and twins? Thanks for your help peoples, appreciate it.
  12. I have my moments.🤦‍♀️ Wondering which one I'm better off binding for flying twins? The one I'm used to using, "Engines throttle control" or both of the lower ones, "Engine 1throttle control" and "Engine 2 throttle control". Or doesn't it matter?
  13. G'day again, Well I think I have solved my own problem above. I had bound the right hand throttle twice. Once near the top of the key binding page at "Engines throttle control" and again down lower called "Engine 1throttle control". I removed the second binding and bingo. All good. Don't know why but the second binding was inverted. Throttle full forward was 0%. I'm guessing the poor game was getting totally confused being given two different values for the same throttle. That would explain why I couldn't recreate the problem in any of the config tools too, now that I t
  14. G'day People, If this is the right place to ask... Just received new Mongoos T-50 throttle tonight (so smooth) and all seemed to go well with installing software, updating firmware, calibrating etc. In game , however, the throttle percentage occasionally flicks around wildly. If I've got the throttle percentage up around 80% and pull it back a hair, it will go down (for example) to 18%, stay there long enough to notice until I push the throttle up a touch and it jumps back to the original 80% or goes up slightly higher. A few seconds later the same thing happens. Or on low throttl
  15. I have this issue too. Looks to me like the problem is that the throttle movement is changing propeller pitch not the throttle.
×
×
  • Create New...