Simworks Studios F-4B/N Phantom II from Just Flight

[doublecool]

Thank you for the heads up and the good news
She is a fine F-4
I am really looking forward to fly her without those CTD

[SiR_RiPPER]

Gents, the patch is coming today.

[gray eagle]

Gents, the patch is coming today.

Just downloaded this new SWS_F-4BN_v1.0_20170420_setup.zip this A.M.
I waned to just say thanks for the fix, it works great now.

ATB

"Butch"

[MDIvey]

New version seems to have fixed the ctd for me... Thanks.

Matt

[gray eagle]

New version seems to have fixed the ctd for me... Thanks.

Matt

+1 Now I can switch from the F4B to a different plane with no hangups in P3d (Crash).

[DaveB]

No dll error here either though I DO have a new set of problems I didn't have before.. all reported at SWS.

I installed the last version as the non-TP model and other than the dll error.. it worked fine but for an intermittent control lockup I only see on this model. Load Manager.. everything.. fine. This time, I installed the TP version thinking that I can use the F4's Configuration module to select the non-TP version if required. Flashed up FSX.. didn't let TP load and found the Load Manager doesn't work. It's as it was before the v1.0 release for non-TP users. Also found that the fwd LH cat isn't working. Aircraft setup on it just jump or judder. The RH and waist cats are fine. I've uninstalled the TP model and have just installed the non-TP model to see how that works

ATB
DaveB

[gray eagle]

No dll error here either though I DO have a new set of problems I didn't have before.. all reported at SWS.

I installed the last version as the non-TP model and other than the dll error.. it worked fine but for an intermittent control lockup I only see on this model. Load Manager.. everything.. fine. This time, I installed the TP version thinking that I can use the F4's Configuration module to select the non-TP version if required. Flashed up FSX.. didn't let TP load and found the Load Manager doesn't work. It's as it was before the v1.0 release for non-TP users. Also found that the fwd LH cat isn't working. Aircraft setup on it just jump or judder. The RH and waist cats are fine. I've uninstalled the TP model and have just installed the non-TP model to see how that works

ATB
DaveB

Non TP works just fine for me in P3D.

[DaveB]

Hi Butch..

I've just uninstalled the TP version I was using in a non-TP environment and installed the non-TP model. All well including the cats on Coral Sea. TBH.. this is no big deal for me as I rarely use TP anyway. It puts my rig closer to meltdown than it would otherwise be. Seemed like a good idea at the time like many other things I have

No surprise that all models have glass too.. something you expect from a model advertised as being for FSX

ATB
DaveB

[Cees Donker]

Hi Butch..

I've just uninstalled the TP version I was using in a non-TP environment and installed the non-TP model. All well including the cats on Coral Sea. TBH.. this is no big deal for me as I rarely use TP anyway. It puts my rig closer to meltdown than it would otherwise be. Seemed like a good idea at the time like many other things I have

No surprise that all models have glass too.. something you expect from a model advertised as being for FSX

ATB
DaveB

Cees

[gray eagle]

After I installed this latest patch, I could change from F4B to F4J (Milviz) to any other aircraft without a CTD in P3d and thought gee, this time it's gonna work, well for some reason it's back to
doing what it use to do. I just had a CTD after I loaded F4B then about 20 seconds later I wanted to see if I could choose another aircraft and P3d folded again

Here is data from event viewer. I also posted this on Simworks forum - Hope Alex takes notice.

Source: Application Error
Date: 4/25/2017 1:27:04 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1a7c
Faulting application start time: 0x01d2bdf0191e0c00
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c7be7c0c-29e4-11e7-acc0-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-25T18:27:04.000000000Z" />
<EventRecordID>244992</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec49b8f</Data>
<Data>c0000374</Data>
<Data>000ce6c3</Data>
<Data>1a7c</Data>
<Data>01d2bdf0191e0c00</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>c7be7c0c-29e4-11e7-acc0-6cf0497dce43</Data>
</EventData>
</Event>


Edit: I just tried it again,selected a F4B model, let it load adjusted the spot view then selected another F4B the preview came up then when I hit the OK button - It it all Blew up.
I checked the event viewer same data as above.

[gray eagle]

After I installed this latest patch, I could change from F4B to F4J (Milviz) to any other aircraft without a CTD in P3d and thought gee, this time it's gonna work, well for some reason it's back to
doing what it use to do. I just had a CTD after I loaded F4B then about 20 seconds later I wanted to see if I could choose another aircraft and P3d folded again

Here is data from event viewer. I also posted this on Simworks forum - Hope Alex takes notice.

Source: Application Error
Date: 4/25/2017 1:27:04 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1a7c
Faulting application start time: 0x01d2bdf0191e0c00
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c7be7c0c-29e4-11e7-acc0-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-25T18:27:04.000000000Z" />
<EventRecordID>244992</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec49b8f</Data>
<Data>c0000374</Data>
<Data>000ce6c3</Data>
<Data>1a7c</Data>
<Data>01d2bdf0191e0c00</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>c7be7c0c-29e4-11e7-acc0-6cf0497dce43</Data>
</EventData>
</Event>


Edit: I just tried it again,selected a F4B model, let it load adjusted the spot view then selected another F4B the preview came up then when I hit the OK button - It it all Blew up.
I checked the event viewer same data as above.

Another edit: I reinstalled the F4B program and this time I use the older GPU card option. I have a GTX 660 which is 6th gen and for now, no issues. The 660 can handle DX10 so it's either
a coincidence that it works now or just plain luck so far.