Jump to content

Cruachan

Members
  • Posts

    3,567
  • Joined

  • Last visited

  • Donations

    75.00 USD 

Reputation

705 Excellent

2 Followers

About Cruachan

  • Birthday 08/15/1947

Profile Information

  • Gender
    Male
  • Location
    Midlothian, Scotland
  • Interests
    Electric Guitar, Photography, Flight Simulation, Astronomy and Gardening (as wife requests)

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

About Me

  • About Me
    Retired Medical Practitioner

Recent Profile Visitors

8,696 profile views
  1. Hi Ray, Perhaps I misunderstood, but I was under the impression all was well while using SSNG whereas you were experiencing strange behaviours with various addons when SSNG was not part of the equation. I was simply wondering whether SSNG was creating unique configurations as part of its method of operation. If these configurations remained in place when P3D was run directly from its desktop icon then perhaps this might explain those anomalies. Uninstalling SSNG should, and again I say hopefully, undo those modifications, if such exist, and would be a way of confirming that SSNG was somehow involved. Regards, Mike
  2. Hi Ray, Dare I suggest you try the effect of uninstalling SSNG temporarily? If SSNG is in some way responsible - does seem likely since everything works when SSNG is in play at the start - then uninstalling should (hopefully) reverse any changes implemented by SSNG and the anomalies, as experienced when P3D is run from the desktop shortcut, will be gone. In theory this should not involve any risk of breaking the sim, but then again Sod’s law might intervene to determine the outcome. Maybe consider backing up the SSNG installation and your User folder before delving deeper into this. Regards, Mike
  3. Could it be that finally there is a dawning realisation amongst those of us in the flight swimming community that there is now a very real risk that we could lose it all and history will confirm that the finger of blame can only be pointed in one direction? The lure of impressive in-your-face visuals along with the vague and possibly disingenuous promise of something better who knows when in the future has proven to be a very effective marketing ploy and is now threatening to destroy the existing flight swimming ecosystem. For what it’s worth, my guess is that MS/ASOBO knew only too well that their product still needed much work but, at time of release, had sufficient substance to wow the enormous gaming community whose priorities are distinctly different from those of the so-called ‘serious’ simmer. The latter expects degrees of simulation fidelity and complexity which extends far beyond the needs of the average gamer whose primary interest is entertainment. There can be little doubt that MSFS is succeeding in this respect. Whether or not it was intended, the consequence has seen legions of core third party developers being lured away from P3D because this is the economic reality if they are to survive. This despite their evident frustrations as highlighted by some posts in this thread. Seems they are stuck between a rock and a hard place. LM has provided a comprehensive mature SDK which continues to invite groundbreaking third party product development and yet those same developers have been enticed away from P3D to a simulator that appears to offer so much promise, but very little substance in terms of practical support and encouragement from the main developer and its financial backer. Meanwhile, LM remain silent and uncommunicative. Perhaps the decision to compete with the new sim has been deemed unnecessary. After all, they already have a perfectly stable sim out there with a multitude of effective, enhancing integrated third party products. Instead, maybe a policy of waiting patiently in the wings while observing the unfolding of an undoubted mess (no further need to elaborate) is being considered as being the more sensible approach. If MS/ASOBO fail to appreciate what is really happening then their initial success could revert into becoming another disaster which benefits no one and will see fortunes turn full circle as developers volte-face and return to the fold. Mike
  4. Count me in. However, I would like to think that as an ardent simmer of flight who believes there is some residual functioning grey matter between his ears and, like most of us here, remains capable of identifying and seeing past any imparted ’wisdom/opinion’ from anyone, including Moderators, who have little or no hands-on experience of the sim in question. Some time ago, I purchased and installed MSFS and, for reasons best known to a psychiatrist, continue to expose myself to those imposed all too frequent and frankly ludicrous updating procedures in the hope that one day I can be persuaded to adopt it as a worthy companion to P3D. That day has not yet arrived. Woe betide anyone, like me, with a slow broadband d/l service. I feel that until ASOBO/MS get their act together we should be taking every opportunity to expose this nonsense. Newcomers need to be warned what to expect before they jump in and part with their cash. Mike
  5. Hi Mike,

    Sorry to bother you, but where in PL do I find the area that I place the M in Rule, which I currently have sent for gaming.

    Regards

    Brian

    1. baxterbj

      baxterbj

      Hi Mike,

      I'm finding that the AF at 61, unlimited frames in P3D, limit frames in Nvidia Profile Inspector to 29.5, FSPS set from 20-30, Vsync on.

      I am pleasantly surprised at the increase in frames, especially in and around YPJT and YPPH in my state of Western Australia, No blurries and quiet Smooth.

      I have PL set to Xhig0-5 as I cant seem to find the M rule anywhere? (Also I'm not that experienced with PL)

      Thankyou for your Kind help.

      Regards

      Brian ([email protected])

       

    2. Cruachan

      Cruachan

      Hi Brian,

      Sorry for the delay in responding.

      Sounds good! Looks like you are making significant headway towards getting the sim to perform the way you would like.

      There is a wealth of information here at Steve Waite's website: http://www.codelegend.com/forums/viewforum.php?f=2

      Process Lasso

      As I mentioned in that post, my current rules for Prepar3D.exe are: XihM5p

      If you refer to Help - View Documentation and under Index select 3. -> 2. Rules column meaning you will see a breakdown:

      X = excluded from ProBalance restraint

      ih = Default I/O priority class: High

      M5 = Memory priority: 5 - Normal

      p = Process will cause the PC to enter a particular Power Profile

      I use the Balanced Power Profile option in Windows which allows the system to return to a Power-saving state (Idle) when no longer under load.

      As with most things, what you chose to implement is really up to you. Prepar3D will trigger a switch to a High performance state without any user interventions so it's quite likely that Rule 'p' is not really required. Doesn't seem to have any negative effects which is why I have not removed it. You could argue that 'ih' and 'M5' are not required either because they represent the default states, but what the heck!

      There are very few hard and fast rules where Prepar3D is concerned as every system and sim setup is different. Sooner or later we all discover that it can take a bit of effort to find what best suits our requirements. This is true especially if you have enhanced the sim with numerous addons and customisations.

      Hope this is of some help to you.

      Regards,

      Mike

       

    3. baxterbj

      baxterbj

      Mike, 

      Thank you for your reply, it’s all beginning to come together.

      I have steered clear of the current path that Ray and Steve were going down as I feared Ray would have a shot at my Australian attempt of the English language, something that we in Aussie have changed to some degree. The Forums certainly take some twists and Turns.

      Thanks again, and I will include Steve Waite’s Site in my favourite list.

      Kind Regards 

      Brian

  6. Hi Mike,

    Got Xih in Process Lasso, but am brain dead in finding  M5p

     

    Sorry to be a pain

     

    Regards Brian

  7. Now, I admit that this doesn't necessarily infer that the 64bit version is on its way, but maybe, just maybe its release should be anticipated by reserving space now on the AVSIM servers to accommodate the daddy of all threads as we all indulge our mixed emotions coming to terms with what just happened. My guess is that by this time next year, if not before, Prepar3D will be available in 32bit and 64bit versions. As with hardware, it is likely that the sim will continue to grow in performance, content and complexity making the transition to 64bit inevitable if not mandatory. Better not to delay than risk becoming sidelined by older technology. In time, Prepar3D could evolve into being the definitive affordable flight simulation adopted by all who are serious about the vicarious experience of realistic human flight. Pretentious rubbish? Perhaps. Place your bets now! Mike
  8. Hi, Don't you think it's interesting that P3D 32bit is still being updated with enthusiasm and apparent unchecked momentum when we all suspect that the 64bit version will soon appear? The assumption is that the latter is intended to replace its mature progenitor, but perhaps instead the plan Is to allow development of both versions to continue in parallel, at least for a while, to facilitate a gradual and stress-limited transition. This would seem to me to be eminently sensible and would be enormously helpful by allowing sufficient time for their commercial clientele, 3rd party developers and, of course, us to refocus on the new platform. Many of us, myself included, have not been affected significantly by the VAS constraints imposed by 32bit and are likely to be happy to stay with v.3.x for some time to come. It may be that we might decide to install the 64bit version alongside v3.x and move over gradually as 3rd party compatibilities and finances permit. I imagine that at first the 64bit version's appearance and performance will be not dissimilar to its predecessor so, if you are happy with what you have now, there will be no compelling reason to rush to make the change but would prefer rather to adopt the less dramatic unhurried approach. It could be a win-win prospect for everyone! Mike
  9. Hi Ryan, Ah, right, so it's a known issue. Seems odd that this appears to be associated with the sun. Thanks, Mike
  10. I'm speculating that this may have something to do with the configuration of the aircraft's headlights/spotlights. The 'artifact' is not seen with other aircraft I've tested nor is it seen when the outside view is selected, only in the VC of the Legacy. All views are of the sun looking east after dawn. KBGE: KVPS: Mike
  11. Hi Bjarne, Looks like the full uninstall/reinstall has broken links between the sim and your various Addons. Like you, I decided yesterday to update to 3.3.5 and on first run Prepar3D crashed without getting as far as the activation window. Fortunately there was enough info provided to point me in the direction of FSLabs Spotlights. Disabling the entries in DLL.XML got me going and subsequently a visit to their website for a compatible update got the module working again. I would uninstall all the affected Addons, check for any updates and then reinstall each one at a time checking all is well as you progress. Much quicker in the long run than trying to troubleshoot this issue. However, the fact that they are all affected suggests there may be a common cause. That may simply be incompatibility with version 3.3.5. This version has been out for some time now so it is likely all your affected Addons will have updates available for download by now. BTW, I only updated the 'Client' and 'Content' components of the 3.3.5 update from LM. Nothing was updated in the 'Scenery' component so was not required. So, problems can and do arise using either method. Regards, Mike
  12. I agree whole heartedly. As my installation has evolved I've lost count of the number of times I have deleted this folder and allowed the sim to rebuild. Does no harm whatsoever. Just remember, and it's been said umpteen times, DO NOT delete the ShadersHLSL folder in P3D root otherwise you will find yourself up the proverbial creek without a paddle......unless, of course, you have remembered to create that backup before launching yourself into the unknown..lol Also, while you are at it, I suggest you check the content of your SceneryIndexes folder. You will find it in the same folder as Scenery.cfg. Corruption of the numbering sequence can and does occur, I know, it's happened to me twice and I still haven't identified the culprit. The indexes should be in an orderly sequence to match the content of your Scenery.cfg. If you see any deviations then simply delete the entire content of that folder (SceneryIndexes) and P3D will rebuild at next run. Mike
  13. Remember Chris Willis (FS Sky World/FS2002)? He was the first, imho, to produce some decent clouds and sky textures for the Flight Simming community. I can well remember all the enthusiastic and excited posts following each of his releases. http://www.avsim.com/topic/16976-thankyou-chris-willis-awsome/?p=103028 Indeed, I acted as one of his testers for a short period. Mike
  14. Thanks again , Rob. I never thought of the relationship in those terms. Hot fixes applied last night, FTX Unification update applied - all reported as being well so 'first light' later today, hopefully Regards, Mike
  15. Thanks Rob. For some reason I was concerned I might lose the lower resolution options but I see that is not in fact the case. The slider in ASCA can now be moved all the way right from 2048x2048 to 4096x4096. Playtime! DXT or 32-bit? In the past (before ASCA) I've been using 32-bit for REX4 TD Soft Clouds and performance could be slightly better although, to be honest, I was never quite sure. Regards, Mike
×
×
  • Create New...