• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

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

C1 not compat with new Corral Sea

I tried the instructions to make the C-1 compatable with the New Corral Sea.

It didn't work, for one thing SHIFT + 2 is already mapped (see pic) so I wouldn't be able to to raise/lower elevators.
Most of the items listed in the conversion instructions were already in the aircraft (pretty much). So it was tail hook ready.
So what to do to see the CS SHIFT + 2 elevator buttons?

image.jpg
 
Hello mate,

The point is that you add the carrier extension as a new window to that model. It is only shift+2 on the F4 because that's how it's panel is mapped;)

This is my Sea Vixen cfg..
[Window Titles]
Window00=Main Panel
Window01=GPS
Window02=Radios
Window03=Throttle Quadrant
Window04=Central Warning Panel
Window05=Switch Panel
window06=TACAN RFN
window07=CV-43 Manager <-------- new window for the Carrier Manager.

The new 2D window added to the panel.cfg..
//--------------------------------------------------------
[Window07]
Background_color=0,0,0
size_mm=1280,720
sizeable=1
visible=0
ident=3061
window_size= 0.7, 0.67
window_pos= 0.015, 0.015

gauge00=..\..\F-4B Phantom II\Panel\CEM!CV43_65_MGR, 0,0,1280,720
gauge01=..\..\F-4B Phantom II\Panel\CEM!CEM_BG, 0,0,1,1
//--------------------------------------------------------

and this line added to VC01..
[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$vc2
gauge00=skysim!CVIX_smoke, 15,0,20,20
gauge01=skysim!CVIX_vortex, 0,0,10,10
gauge02=skysim!CVIX_flame, 40,0,20,20
gauge03=CVIX!Radalt, 225,675,207,208
gauge04=CVIX!Autopilot, 0,0,308,392
gauge05=CVIX!Trim, 308,172,83,226
gauge06=CVIX!Hyd2, 0,395,200,200
gauge07=CVIX!Hyd1, 0,595,200,200
gauge08=CVIX!CWP, 479,3,537,397
gauge09=CVIX!ComRadio, 456,399,491,393
gauge10=CVIX!OilTemp2, 210,400,200,200
gauge11=CVIX!Tacan, 3,915,110,102
gauge12=CVIX!XpndrRepeater, 178,940,120,44
gauge13=CVIX!ARTrim, 1,789,102,102
gauge14=CVIX!Stopwatch1, 464, 795 ,183,222
gauge15=..\..\..\..\Aerosoft\F-14A\FLOLS\CV63_FLOLS!FLOLS_CV63
gauge16=CarrierExtensions!CarrierExtensions,0,0,0,0 <---------- Carrier extensions gauge added
//-------------------------------------------------------------
gauge81=RFN_CarrierGauge!TACAN_Navigation, 0, 0, 0, 0, Nav2
gauge82=RFN_CarrierGauge!CustomCatapult, 0, 0,
gauge83=RFN_CarrierGauge!Approach_Ctrl, 0, 0, 0, 0, 0.0
gauge84=DSD_Sound_Gauge!Sound, 0, 0,

//--------------------------------------------------------

That's it for the panel.cfg. You have to add the following to the end of the aircraft.cfg:

[carrier_extensions]
aoa_threshold=11.5
aoa_waveoff=13
launch_bar=17.6, 0.0, -7.2

The values on all of these changes from aircraft to aircraft but this entry has to be in place even if the entries for aoa threshold and waveoff are incorrect. You can take the launch_bar position from the [launchassistance] entry if you have it.

Good to go;)
ATB
DaveB:)
 
Butch..

It so happens that I have the C1 so I've added the relevant lines and entries for you. Open your C1 panel.cfg and add the lines/entries as highlighted:

[Window Titles]
Window00=main
Window01=GPS
Window02=Throttles
Window03=Radio
Window04=Electric popup
window05=CV-43 Manager // <------- add this line

Add this window after window04:

[Window05]
Background_color=0,0,0
size_mm=1280,720
sizeable=1
visible=0
ident=3061
window_size= 0.7, 0.67
window_pos= 0.015, 0.015

gauge00=..\..\F-4B Phantom II\Panel\CEM!CV43_65_MGR, 0,0,1280,720
gauge01=..\..\F-4B Phantom II\Panel\CEM!CEM_BG, 0,0,1,1
//--------------------------------------------------------

Then add this line to VC01:
[Vcockpit01]
file=Left.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024
texture=$left
gauge00=ST_Tracker!ADI, 622,261,183,178
gauge01=ST_Tracker!Altimeter, 243,470,168,162
gauge02=ST_Tracker!ASI_400, 239,270,172,166
gauge03=ST_Tracker!turn_and_bank, 426,458,188,182
gauge04=ST_Tracker!VSI_4, 630,468,168,162
gauge05=ST_Tracker!RMI, 436,272,169,165
gauge06=ST_Tracker!Rad_Alt, 55,469,165,162
gauge07=ST_Tracker!DG, 824,467,168,162
gauge08=ST_Tracker!HW_FlapGear, 800,71,168,162
gauge09=ST_Tracker!clock, 650,82,134,133
gauge10=ST_Tracker!DC Voltammeter L, 673,715,99,96
gauge11=ST_Tracker!DME, 824,712,187,187
gauge12=ST_Tracker!DC Voltammeter R, 717,828,98,96
gauge13=ST_Tracker!Sw_Dummy_Compass, 149,273,32,51
gauge14=ST_Tracker!VOR1_Indicator, 822, 273 ,168,158
gauge15=ST_Tracker!SW Panellights, 236,739,71,70
gauge16=CarrierExtensions!CarrierExtensions,0,0,0,0 // <----- add this line.

Next, open your C1 aircraft.cfg and add this to the bottom:

[carrier_extensions]
aoa_threshold=11.5
aoa_waveoff=13
launch_bar=14.087, 0.000, -7.968

Note that the aoa threshold and waveoff values may well be off the mark. I've no idea what they are for the C1 so you'll have to tweak them in yourself. The launch_bar line was taken from the [launch_assistance] entry in the C1 so should be there or thereabouts.

Have fun out there;) Oh.. and this will open as shift+6.
ATB
DaveB:)
 
... and to prove it works..

c11.jpg


c12.jpg


Just adding a few deck models with the click spots may not look as grand as the presets but it gives the deck a bit of life and you can trap and launch without having to change cfgs. The secret is don't be afraid of adding the Carrier Extensions. Anyone who can add the RFN Tacan which to my mind, can be trickier, can add this. When you've done it once, it takes about a minute to add the panel and aircraft.cfg entries to other models;)
ATB
DaveB:)
 
And you managed to make it down the lift without falling through too!!

Excellent mate.. glad you're sorted:encouragement:

A question for you. Did you have any models parked on the other lifts? Just wondering if there's some strange correlation between the lifts being visible but not solid sometimes. I doubt it as Alex has already said it's random and for no apparent reason.

The C1 gets off the deck in short order doesn't it!! I noticed it airborne before it had crossed the bow.

EDIT.. to your last post Butch, the shift+ number is always one number greater than the window it's opening. The Carrier Window is [window05] on the C1 so to open it will be shift+6;)
ATB
DaveB:)
 
DaveB said:
And you managed to make it down the lift without falling through too!!

Excellent mate.. glad you're sorted:encouragement:
Click to expand...


Thanks,

DaveB said:
A question for you. Did you have any models parked on the other lifts? Just wondering if there's some strange correlation between the lifts being visible but not solid sometimes. I doubt it as Alex has already said it's random and for no apparent reason.
Click to expand...


No, I haven't converted any other third party aircraft yet. But with your examples., I sorta get the gist of it. :adoration:
 
It works just as well on the Milviz F-4J/S, too.
Also the Virtavia A-4, the Razbam A-6/EA-6/A-7 packs, etc.

Dave
 
Cheers Dave. I was just about to lob it onto the Virtavia Skyhawk but of the 1001 paints knocking around, there's not one for VA-153:banghead: Any takers???

Oh.. it works on the Virtavia A3 Skywarrior too:encouragement:

ATB
DaveB:)
 
P3d Crashed Again

I landed aboard the New CS in a SWS F4B and then switch over to a converted third party aircraft that can use the elevators like the F4 can and it crashed, again.

I loaded the event viewer and copied the date and sent it over to Alex, maybe his coders can decipher what's going on.

From what I can tell in the event viewer, a file called Phantom_RS.dll may be at fault.
 
Tried it again

This time I landed on Enterprise in C1A and then switched to a SWS F4 - no problem - but when I switched from SWS F4 to a Milvix F4 then P3d Crashed.


Log Name: Application
Source: Application Error
Date: 4/9/2017 1:21:16 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MV_F-4J_Sys.dll, version: 1.4.0.8, time stamp: 0x58d3b1d8 <<<<< this is when I sent from SWS F4 to Milviz F4 then it crashed
Exception code: 0xc0000096
Fault offset: 0x00001591
Faulting process id: 0x1414
Faulting application start time: 0x01d2b15d5f96d07e
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll
Report Id: 515ad6a1-1d51-11e7-8c59-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-09T18:21:16.000000000Z" />
<EventRecordID>243653</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>MV_F-4J_Sys.dll</Data>
<Data>1.4.0.8</Data>
<Data>58d3b1d8</Data>
<Data>c0000096</Data>
<Data>00001591</Data>
<Data>1414</Data>
<Data>01d2b15d5f96d07e</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll</Data>
<Data>515ad6a1-1d51-11e7-8c59-6cf0497dce43</Data>
</EventData>
</Event>


THis switching A/C while onboard any carrier is causing havoc in P3d V3.4 if two different F4's are involved. Hummmmm
 
Yup.. that patch was specifically for P3D 3.4 and not required for earlier versions or FSX. I think Butch already has that installed so maybe it's not as fixed as it might be.

ATB
DaveB:)
 
SiR_RiPPER said:
I think MV had a problem with the latest 3.4 and released patches a week ago or so. The crash is from F4J_sys.dll
Click to expand...

Before they released a patch, P3D would CTD after the patch P3d did not CTD. I once just renamed the file and everything was fine.


I was just doing traps on the Nimitz with the C1 then switched to a F18 and that went good, then went to a SWS F-4 and that was Okay then went to a MV F4 and that was the end of it (It CTD)
 
If you renamed the file then you lost the systems of the F4...at least from what it sounds like what you're doing...so although it doesn't error it's not working correctly?
 
I get a crash to desktop every time I end a flight or change aircraft which is getting a little tiresome. I'm an fsx steam user with Steve's dx10 fixer. I will get round to reporting it to SSW but in case you're around Alex I thought I'd mention it here.

Matt
 
You must log in or register to reply here.
Back
Top