Jump to content

SR-22 Driver

Members
  • Posts

    20
  • Joined

  • Last visited

About SR-22 Driver

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SR-22 Driver's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. This appears to be the issue. Setting EZDok correctly for the 330 seems to have solved the acceleration issue - I have no clue how it could cause it and how EZDok figured out a way to code it out. Ahh the complexity of our hobby. Looking forward to getting to just P3D V5 and FS2020. Right now I am running FSX Steam for a Concorde and a Jetstream, P3D V3 for I can't remember why, P3D V4 for things like Aspen, other add-ons and because my older machine can't run V5, P3D V5 for some of the newer scenery and FS2020 for VFR only GA. Maybe I should try XPlane?! Tx for your help. Richard
  2. I think I might have found the issue. EzDok V3 has a button in the Effect Studio that says "Taxiing Speed Fix". Hidden down at the bottom and added recently. Says they specifically added it for Aerosoft and another vendor. You have to select file - update camera set after selecting it for it to stick in another menu panel. Not so intuitive. May help other people who hit this issue... I will test and report back if this was it - fingers-crossed. Richard
  3. I have read the other threads saying low frame rates can cause this behavior and it can't be fixed. The plane works fine in P3D V4.5. After upgrading to V5 I have better, more stable frames, and it happens nearly every time I fly the plane. It specifically happens when I switch to an outside view or switch to another app like navigraph charts. Pretty much guaranteed to come back to a plane accelerating uncontrollably down the taxiway. I have locked my frames at 30. Running: P3D V5.0 HF2 I7-7700k O'clocked to 4.8 NVIDIA 2080TI 11GB VRAM 1TB M2 SSD 32 GB Ram ActiveSky P3D EZDOK V3 2 Screens - one for P3D, other screen for browser/Navigraph/ActiveSky etc I have scaled down my settings to avoid a low frame spike. No Luck. This does not happen with any other plane. It is unusable. Any suggestions would be welcomed. FWIW I am switching to P3D V5.1 HF1 and will report back if I can replicate there. Richard
  4. Thanks Dave. I'll take a look, I fly a combo of low and slow highly-detailed scenery with GA as well as liners. The current config was a holdover form simply getting GSX airport editor to work with EZDOK to edit airport positions. I got lazy and let it be my default. This is a great reminder to clean up my saved configs and use different ones for each type of flight I do. Used to have to be religious about it with 32bit FSX and P3D - got lazy with P3D V4! Enjoy the holiday season! Rick
  5. Thanks for your quick responses and feedback Mathijs and Dave - sorry for the wild goose chase.
  6. Since you asked To be clear - the load time is long from P3d startup to the scenario editor screen (2:40 sec+), but quick to load from the editor until i am fully in the sim (40 seconds-ish).
  7. Time to call this Gremlins. Just did a two new saved scenarios in the exact same spot, at the exact same time, from both within the sim and within the scenario screen at OMDB. Both worked... If I call up my original scenario file with the issue, it still does not work. Must have been some issue with that particular scenario file? I guess... I do save and replace on top of old Delme files; that is what I do for temp scenarios I want to save - just keep resaving on top of them. But I tested this as well by saving on top of the bad one and it is still working. If it happens to someone else in the future, at least this thread is here and may help. Thanks for looking into this. I think it can be closed - I tried 10 variations to replicate and was unable to. Rick Would appreciate some of your thoughts - should I start a different thread or PM you? Since it is probably unrelated to this particular issue? FWIW I am a 2 minute 20 second load time to the scenario screen... (after removing UTLive from startup process)
  8. Loading a scenario simply saved with the A330 as a vehicle from the default scenario worked too. Think it is maybe FlyTampa OMDB. Any shared texture files there maybe? My next step is a reinstall of FlyTampa just to see... Rick
  9. Interesting. Did not happen at default P3D startup and airport: Went all the way into the sim after picking Swiss A330 at the scenario screen. Saved Scenario from within Sim Exited and went back in, then selected scenario from menu and went into sim Trying again by creating scenario in scenario screen and saving. Then exiting P3d completely and then loading the scenario to confirm.
  10. I have cleared shaders as part of the debug. GCard has been installed for 6 months. I will give the wipe a try but if I can replicate at another airport, it must be something else. Stand by P3D is a hog to load
  11. No tweaks or overclocking. Using latest driver from early December. It happens with or without EZDOK, with or without REX Environment Force. I am going to try a different airport and see if I can replicate. Scenario attached delme.fms delme.asc Delme.abx Delme.fxml Delme.wx OMDBOOSA01.rt2
  12. I should also add, in trying to debug the problem, I did I complete reinstall of the plane (rebooted multiple times, no AV, CC-cleaner registry check just in case) . I also reinstalled the MS C++ libraries. I think I created the offending scenario by saving it in sim, not rom the scenario screen and saving it. Also used the Swiss A330. Again, not a big deal as you can work around it by building the scenario on the ground. Thought it may be helpful if you are trying to get ahead of the curve on bugs (if it is one - and not a config issue for me). Tx, Rick
  13. 2080 TI with 11GB 16GB Mainboard memory I7-7700K Win 10 latest update Note the pattern of loading I did - works fine in all other circumstances when I do not load a saved scenario. Rick
×
×
  • Create New...