Jump to content

Paul K

  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

372 Excellent

About Paul K

  • Rank

Profile Information

  • Gender
  • Location
    Norwich U.K.

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

2,303 profile views
  1. As an aside, but related, I had a livery for the JPLogistics-modded C152 which caused a CTD every time I tried to use it. I examined it, but never got to the bottom of why it was causing a problem. It's strange how seemingly small things can affect the entire sim.
  2. So far, so reasonable. I've seen two Delta A330s land at Seattle, turn off at the end of the runway, and then stop. Everything on approach behind then goes around. Certainly, the models look better than the default Asobo ones. Not there yet, but this is well worth persisting with.
  3. You've offered me advice on software that you clearly know nothing about, and now you choose to be rude. Conversation over, and you're now blocked.
  4. Simple Traffic only replaces liveries. The AI models remain the stock Asobo ones. When I said I haven't seen anything ugly about ST, I'm referring to the quality of ST's liveries, since that is all ST provides. As said, ST doesn't have its own models, nor does it place them or govern their behaviour. What I am concerned with is whether the liveries in ST and FSLTL might conflict. Could someone who owns Simple Traffic offer me some advice, please. I'd be grateful.
  5. Well, I haven't seen anything in Simple Traffic that is particularly ugly. I think ST's liveries are perfectly acceptable. It's the possible conflicts of having them both installed at the same time that is my concern - or maybe there are even advantages to having both. Anyone know for certain?
  6. Can someone please tell me if there are conflicts between FSLTL and Aerosoft's Simple Traffic ? Can I have both installed at the same time ?
  7. DX12, and doing circuits at Chicomick's freeware Duxford, around 1000 ft up, the runway markings are very much sharper with TAA than with DLSS. I'm using a 3080Ti, with a 1440p monitor, render scaling set to 200, FidelityFX sharpening set to 100, frames locked at 30. I'll stick with DX12 and TAA, and look forward to further refinements from Asobo. Right now, the sim has never looked or performed better.
  8. Ask and thou shalt receive 😉 Below is a cut and paste from SWS' Facebook page a couple of days ago - it's nice reading: It's been a while since we did a detailed update on the Kodiak, hasn't it? With Sim Update 10 now released, we are finally back in the fray and working on the final details for the Kodiak. First of all, the new versions of the Kodiak, wheeled and amphibian are coming with beta range support -not the fake spoiler kind of beta range, but actual propeller drag from changing the pitch. You will be able to control your taxi speed using the power lever just like in the real aircraft seamlessly, using the simulator's default throttle bindings! Power users of SPAD.NEXT or FSUIPC who want to use beta range without toggling reverse will need to map their power levers to a new variable which will give them full range control (will be in the manual). Additionally, the Kodiak will feature a working manual override lever. While FCU and throttle failures are not modelled in the aircraft, we didn't feel well seeing the lever inoperative and figured out how to make it work. Secondly,the Kodiak will come with support for the new, default version of the NXi that released with SU10. Currently, you have to download a special build from the Marketplace to be able to see the latest NXi in the Kodiak, but this will be a one-time release that WT did, in order to allow current aircraft to work with it. In the future, all aircraft will need their panel files modified to use the default version. The new version of the Kodiak (wheeled and Amphibian) will point to that to make sure that the aircraft is future-proof. The new version of the NXi also allows the creation of plug-ins, but it is currently undocumented. We want to use that feature in the future to initially add the long missing flap & trim indications to the MFD and maybe improve some aspects of the avionics. Thirdly, engine stress has been reworked. Random engine failures are still present, but engine replacement now happens much sooner, so users that have almost reached the end of life of their engines will no longer have to resort to file tinkering to replace their engines. So you will still get the odd failure, but it will not be as frequent unless you hot-start the engine and severely damage it. In that case, your current flight will have a higher probability of failure, but your next one is likely to be with a fresh engine. Other changes have been also introduced to the failure system, also coping with MSFS sometimes starting the propeller at ultra-high RPM which would lead to instant failure of the engine. Then, the flight model has seen some work. Some changes to the core flight model after SU8 would cause the plane to drop like a stone at low speeds. We have found the cause and improved pitch authority, so this has been addressed. An added bonus is that you are now able to rotate the aircraft at lower speeds. Another commonly reported problem, the aircraft's pitch sensitivity, has been adjusted. We have reduced the pitch response of the elevator relative to the yoke, which will make fine control much easier for the majority of desktop yokes that have a very short throw. The current pitch response is smoother and finer, but the aircraft still requires proper trim discipline to fly. Lastly, more rudder trim is required on take-off, which brings it closer to available reference and our manual. The Amphibian variant is ready and matches the wheeled version in features 1:1. The plane can turn easily into the water even at slow speeds, and water take-offs have to follow proper procedure. The landing gear is fully functional with its audio cues, test mode and circuit breakers working as they should. The only thing we aren't 100% happy with is a slight bouncing that may be experienced in the 30-50kts speed range, which has to do with MSFS' water physics. We have been able to minimize it to the point where it is not a problem, and it goes away once you get on the step at 50-55kts. Barring any unforeseen problems, we anticipate release in a couple of weeks on our website and 3rd party stores, along with the update to the wheeled variant. Updates to Microsoft Store for PC and Xbox will take a bit longer as they have to be processed by the Marketplace team. Additionally, because of the Kodiak & DHC-7 we are constantly making big leaps in our capabilities. Both aircraft have served as great test beds to learn new tricks within MSFS' coding ecosystem, leading to some very sophisticated features that will be present in the PC-12 and NG. Additionally, we are making quantum leaps with avionics development, making full use of MSFS' JavaScript/HTML capabilities. While it has taken a while, we wanted to do it right and the end result will be crisp gauges with minimal performance impact. This will have a huge impact on the PC-12 as we want the plane to perform as well as it looks -and we know you haven't seen it yet!
  9. Little Nav Map is excellent, 100% recommended.
  10. A significant update for the wheeled version is also coming, according to the SWS Facebook page - probably to be released at the same time as the amphibian.
  11. Thanks very much for that - I've added my vote.
  12. Yep, that's exactly the sort of thing that could be done. I wonder if this 3rd-party avatar thing is worth suggesting on the official forum ?
  • Create New...