UPLOADED: Spitfire Mk.VA Package - Page 2
Page 2 of 2 FirstFirst 12
Results 26 to 35 of 35

Thread: UPLOADED: Spitfire Mk.VA Package

  1. #26
    While Andy's suggestion may or may not did the complete trick, reducing the screen resolution also helped. So, when selecting either the Mk.II or Mk.V in the UI, their Initializer comes online but as soon as I hit 'Fly', the process is cancelled and the selected aircraft flies in 'stock mode' (not RSM). When I end the flight, their respective CleanUp.exe processes run. Back in the UI, the Initializer is active again but when I hit 'Fly' a second time, CFS3 usually crashes.

    EDIT: I played some more and sometimes there is a process called 'ClickDisabled.exe' that seems to prevent any mouseclick in the UI, even in programs outside of the CFS3 window...

    ACC Member, ETO and PTO contributor & librarian

  2. #27
    The only part of that that should be happening is the initializer and cleanup routines are appearing and disappearing when they should. But the initializer is not launching the Spitfire module. It seems as if it is having a hard time recognizing what the CFS3 window is doing. Is there anything that isn't stock with your UI or the CFS3 window title?

    The click disabled feature is to prevent you from starting a flight before the RSM is ready. It should not be active when the CFS3 window is not up and active.

    Something seems to be different about how your system handles programs' windows. But it worked for you in the past, so I'm really confused.

  3. #28
    Out of curiosity, what happens if you replace the exe files from the Spitfire Mk.II RSM (just the ones for the root CFS3 directory and the systems folder - but NOT the SpitMkII subfolder)?

  4. #29
    Quote Originally Posted by gecko View Post
    Out of curiosity, what happens if you replace the exe files from the Spitfire Mk.II RSM (just the ones for the root CFS3 directory and the systems folder - but NOT the SpitMkII subfolder)?
    Unfortunately, that doesn't work either... But,

    1. when only having the Mk.II installed: In roughly 2 out of 3 QC flights, the RSM enganges succesfully. However, it not very stable, resulting in repeated CTDs when clicking 'Fly', ending the mission, or back in the UI when selecting a different aircraft.
    2. when only having the Mk.V installed: Roughly 1 out of 8-10 QC flights sees the RSM enagage succesfully. It is the more stable version (haven't experienced a CTD yet). When I end a mission after a succesful RSM flight, the second flight in the same session never sees the RSM engaging as well. When selecting different Mk.V Spits in the UI, I sometimes see the prop change position, so something is going on... (I noticed that with a RSM flight, the prop often hasn't got one blade in the 12 o' clock position when starting the engine.)

    ACC Member, ETO and PTO contributor & librarian

  5. #30
    So what results do you get when running the combination I suggested? Using the main RSM files from the Mk.II but overwriting the SpitMkII subfolder with the one from the Mk.V package I expect you would keep the stability of the Mk.V, but have it start more consistently like the Mk.II. But to be honest, all of the loading failures and CTDs are way more than what I've encountered with either package.

    I'm happy to hear the CTDs are gone on the Mk.V. I put a fair amount of work into removing potential issues (even though I wasn't having CTDs, there where some aspects of the code which could allow them) so I'm glad that at least has paid off.

    The prop changing position in the UI (as well as the cockpit door being open and the elevators drooping) are all indications that the initializer script is being loaded. If it correct to presume that if you see those things in the UI that the RSM launches successfully when you start the mission, or is that not always the case?

  6. #31
    Quote Originally Posted by gecko View Post
    So what results do you get when running the combination I suggested? Using the main RSM files from the Mk.II but overwriting the SpitMkII subfolder with the one from the Mk.V package I expect you would keep the stability of the Mk.V, but have it start more consistently like the Mk.II. But to be honest, all of the loading failures and CTDs are way more than what I've encountered with either package.

    I'm happy to hear the CTDs are gone on the Mk.V. I put a fair amount of work into removing potential issues (even though I wasn't having CTDs, there where some aspects of the code which could allow them) so I'm glad that at least has paid off.

    The prop changing position in the UI (as well as the cockpit door being open and the elevators drooping) are all indications that the initializer script is being loaded. If it correct to presume that if you see those things in the UI that the RSM launches successfully when you start the mission, or is that not always the case?
    No joy with the mix either...
    And no, even though the UI animations may indicate that the scripts are active, in-flight they do not always show. I really wonder what is blocking the execution of the scripts. I've tried turning off the AV programs (Norton and MS Defender) but that didn't improve things.

    Well, no rush. I tried the Mk.V when on occasion everything worked and I love it! It's very immersive - and sometimes annoying when a component fails and you can't find the cause; last time the RSM worked, the fuel pressure suddenly dropped, the engine quit, which was most unfortunate as I was being chased to the deck by a 109. Luckily I managed to make a belly landing in a nearby field and walked away...

    ACC Member, ETO and PTO contributor & librarian

  7. #32
    On flights where you see the animations in the ui, but the module doesn't load when the flight starts, does the initializer script appear in the task manager?

    I'm curious as to the cause of your engine failure. Was it lots of negative g (the shilling orifice is installed, but it doesn't provide full protection from negative g), or maybe overreving?

  8. #33
    Member sixstrings5859's Avatar
    Join Date
    May 2011
    Location
    Sulphur,South West Louisiana in the good'ol USA
    Age
    56
    Posts
    2,929
    Blog Entries
    1
    Been enjoying the new Spitfire Mk Va's ! Don't use the RSM option but love them never the less. There is everything to like and nothing to dislike. I know a lot of work went into the RSM part but it is too much for me to process while trying to stay in the air. The sounds ,cockpit,attention to detail are marvelous. Anxious to get the new ones coming up !Think i will soon have as many Spits as Mustangs and Bf-109's ,if not more. Can't have too many Spitfires in my book ! Regards,Scott

  9. #34
    Quote Originally Posted by gecko View Post
    On flights where you see the animations in the ui, but the module doesn't load when the flight starts, does the initializer script appear in the task manager?

    I'm curious as to the cause of your engine failure. Was it lots of negative g (the shilling orifice is installed, but it doesn't provide full protection from negative g), or maybe overreving?
    RE Q1: When I could view both the task manager and CFS3, it did start but immediately shut down again when starting a flight. Right now it seems impossible to have RSM start CFS3 in a window (it didn't before either, but reducing the screen resolution somehow resulted in a windowed CFS3 session ). I think I'll re-install ETO somewhere in the weekend and start again.
    BTW, there seems to be a message window flashing by after selecting the era and just before the small CFS3 splash screen opens. It is so fast gone that I can't read the contents.


    RE Q2: I don't know and I didn't have the time to find out, as I was already low with that 109 on my tail. Overrevving certainly is a possibility. Please don't take the 'annoyance' as criticism; I thought it was one of your programmed random failures. It just occurred at a very inconvenient moment but was probably the result of my engine-abusing aircraft handling earlier in the fight .

    ACC Member, ETO and PTO contributor & librarian

  10. #35
    Hmm, very strange. The initializer script should exit when the mission starts. So that part is right. But right before it exits, it should be launching the module scripts for the aircraft. It could either be that something else shuts it down before it can launch the scripts and exit on its own, or that it launches the scripts but they are shut down immediately. Both possibilities seem to point to some sort of anti-virus issue, but you would think that the AV software would stop it every time.

    For your engine failure, I didn't see it as criticism, I just wanted to make sure my code wasn't actually messing up and making things harder than they ought to be.

Members who have read this thread: 102

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •