Iris F-16D in V4
Results 1 to 8 of 8

Thread: Iris F-16D in V4

  1. #1

    Iris F-16D in V4

    Hello all,

    has anybody successfully got this working in v4.4? I have it in but it causes a CTD after about 5 minutes.

    Thanks,
    Dale

  2. #2
    It works for me (P3Dv4.5). Does your Windows Event log give any clues about the faulting module?

    Henk.
    Last edited by hschuit; July 5th, 2019 at 07:11.

  3. #3
    I had it in 4.2 just fine, skipped the 4.3 update and went with 4.4. I'm getting caught up on add-ons and will add the Iris Viper and report back. Then I probably need to go ahead with 4.5 now that Tacpack is updated, wish updating was as easy as it is on DCS.

    UPDATE: Checks good on deck, no issues with all DED menus, I only forgot the light .fx files and I need to check the stock P3D "air noise" sound. I use the outside P3D/alternate manual install on my add-ons.
    Last edited by Victory103; July 5th, 2019 at 12:37. Reason: it flies
    Fly Navy/Army
    USN SAR
    DUSTOFF/ARMY PROPS

  4. #4
    According to the event log:

    + System
    - Provider
    [ Name] Application Error
    - EventID 1000
    [ Qualifiers] 0
    Level 2
    Task 100
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2019-07-06T04:51:51.702313700Z
    EventRecordID 47551
    Channel Application
    Computer MSI
    Security

    - EventData
    Prepar3D.exe
    4.4.16.27077
    5bfdbb35
    VRS_TacPack.dll
    1.5.0.6
    5c4002f8
    c0000005
    0000000000133f30
    25ac
    01d533b582e1e58b
    D:\P3D V4\Prepar3D.exe
    D:\P3D V4\Modules\VRS_TacPack\VRS_TacPack.dll
    807a111d-9533-454c-b7cb-664d0fa26a90
    The strange thing is that I haven't had any issues with any other aircraft. Any ideas?

  5. #5
    I didn't think that one was Tacpacked. I may be stating the obvious here, but it looks like the faulting module is VRS's Tacpack.dll. I have mine set to ask me if I want it to load it or not at sim start. You can set that in the Tacpack Manager I believe. Do that, tell it not to load and see if it still CTD's.
    Very Respectfully,

    Jim 'Doc' Johnson, SMSgt, USAF (Ret)
    Fac Fortia Et Patere
    ____________________________________________
    Win 10 Pro 64 Bit, i7 6700K 4.0 GHz, ASUS MAXIMUS VIII IMPACT Z170 Mini ITX, G.SKILL TridentZ 16GB DDR4 4000, ASUS GeForce GTX 1080 8GB STRIX, P3D 4.5.12.30293

  6. #6
    Quote Originally Posted by docjohnson View Post
    I didn't think that one was Tacpacked. I may be stating the obvious here, but it looks like the faulting module is VRS's Tacpack.dll. I have mine set to ask me if I want it to load it or not at sim start. You can set that in the Tacpack Manager I believe. Do that, tell it not to load and see if it still CTD's.
    To my knowledge it isn't tacpcked. I have tried to disable tacpack and that seems to do the trick but it's strange that none of my other tacpack aircraft have this issue. Hey ho it works without tacpack.

  7. #7
    I merged the stock VC with the Triple 6 model with no issuses

    But it limits you to certain paints and no visual ordinance

  8. #8
    Other than the afterburner, I am having no problems at all/

    Bill

Members who have read this thread: 0

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
  •