Jump to content

Recommended Posts

Greetings,

 

I've been playing SF2 for just over a month and wow, its an improvement over the original series for sure. Recently, I got to playing with Spinners F-100G, and started modifying it. I got a working HUD in it (thanks to the search function), but I want to step it up even more.

 

Ideally, I want to drop LGBs from it. I've managed to hang a targeting pod on it, and it does drop and hit the targets. When I select a target, it shows up on the HUD (via a neon green/blue diamond). There's also a green box in my upper right corner with the view from the targeting pod.

 

My question is, is it possible to place another box/instrument/screen in the cockpit? Im not talking about 3D modeling as its way above my pay-grade, but just a simple tweak. Using the F-100D_68 pit, there is a blank spot in the cockpit on the lower left of the instrument panel.

 

I've searched the knowledge base, but couldnt find anything. If someone could point me in the right direction, or where to start for ME to start monkeying around with it, I'd appreciate it.

 

Thanks again.

 

EDIT -- some pictures to describe the above.

Picture 1 -- working HUD

Picture 2 -- Blank spot that I would like to put a screen

Picture 3 -- Targeting pod. Gonna try to put a PAVE PENNY pod as I mess around with it more.

post-9057-0-39091600-1358030198_thumb.jpg

post-9057-0-88537000-1358030205_thumb.jpg

post-9057-0-56324500-1358030214_thumb.jpg

Edited by bucklehead101

Share this post


Link to post
Share on other sites

To have a separate radar/LGB screen in the cockpit, you have to have a dedicated part of the cockpit for it. That part has to have its own texture too. The RWR screen is a prime example. Now, it could be POSSIBLE that blank panel in the lower left side complies with both of those, in which case, it's pretty easy.

 

If not, it probably can't be done unfortunately.

 

FC

Share this post


Link to post
Share on other sites

I got the PAVE PENNY pod attached to the fuselage like I wanted, now its just messing with the cockpit. FastCargo, I'm assuming when you mean dedicated, that it means it has a dial, or a stand in. I think I know where to look (cockpit.ini), and found the following:

 

Instrument[001]=AirspeedIndicator

Instrument[002]=MachIndicator

Instrument[003]=AttitudeIndicator

Instrument[004]=Altimeter

Instrument[005]=Accelerometer

Instrument[006]=VerticalVelocityIndicator

Instrument[007]=HSIWheel

Instrument[008]=CourseArrow

Instrument[009]=BearingMarker

Instrument[010]=RangeCounter

Instrument[011]=StandbyCompass

Instrument[012]=Slipball

Instrument[013]=FuelIndicator

Instrument[014]=Tachometer

Instrument[015]=FuelFlowIndicator

Instrument[016]=ADI_BankIndicator

Instrument[017]=HUD

Instrument[018]=Reflection1

Instrument[019]=Reflection2

Instrument[020]=CenterMirror

Instrument[021]=TurnIndicator

Instrument[022]=ClockHour

Instrument[023]=ClockMinute

Instrument[024]=ClockSecond

Instrument[025]=CautionLight

Instrument[026]=OverheatLight

Instrument[027]=FireLight

Instrument[028]=Compass

Instrument[029]=FuelFwdIndicator

Instrument[030]=LandingGearLever

Instrument[031]=ExhaustTemp

Instrument[032]=OilPressure

Instrument[033]=StickRoll

Instrument[034]=StickPitch

Instrument[035]=ADI2_Roll

Instrument[036]=ADI2_Pitch

Instrument[037]=PR

Instrument[038]=RadarLockLight

Instrument[039]=RadarRangeDial

Instrument[040]=CourseCounter

Instrument[041]=CourseDeviation

Instrument[042]=CoursePointer

Instrument[043]=RPM_small

Instrument[044]=RWR

Instrument[045]=AltBarbar

Instrument[046]=GlideSlope

Instrument[047]=LightLowFuel

Instrument[048]=ThreatLaunchLight

Instrument[049]=ThreatSAMLoLight

Instrument[050]=ThreatSAMMidLight

Instrument[051]=ThreatSAMHiLight

Instrument[052]=ThreatAAAALight

Instrument[053]=ThreatAILight

 

As far as I can tell, there is nothing signifying a blank plate. I thought there would, as the F-100D early and F-100D late have their instruments jumbled around like the real thing, but they must be different cockpits all together.

 

Thanks for the help though!

Edited by bucklehead101

Share this post


Link to post
Share on other sites

Well, you wouldn't find just a 'blank plate' entry in the ini file. You actually have to look in the LOD and OUT files to see if there is such a thing.

 

But since the TW sims don't give you the OUT files and the LODs are locked away...you could be screwed.

 

However, there is an another option.

 

Find and extract all the graphics files for the F-100. Eliminate the external model files.

 

Eliminate all the graphics files except BMPs.

 

What you have left is mostly dial faces.

 

Find a dial you aren't using or wouldn't miss and replace the BMP with a blank, black BMP. Find the corresponding entry in the cockpit.ini. You now know the node name of the dial you can turn into a radar/EO screen...

 

FC

Share this post


Link to post
Share on other sites

You had me curious, so I've started checking.

 

First, the good news is that 'plate' appears to be a separate mesh.

 

Second, the bad news is that it appears to be covered by the cockpit BMP file (PIT2_F-100D_64.BMP)...so you're screwed with using that 'plate'.

 

FC

Share this post


Link to post
Share on other sites

Looks like I'll be checking out instrument diagrams and picking which one to swap out. Thank FC!

Share this post


Link to post
Share on other sites

Without me looking into it, maybe you could use the UHF COMM in the top left of the panel?

 

Dels

Share this post


Link to post
Share on other sites

Just moved back on campus for my last semester, When I get a chance, I'll take a look at doing that. Good idea though, dont really use that much.

Share this post


Link to post
Share on other sites

wouldn't it be FAR easier to simply swap the Hun pit for something that already HAS the scope CRT? Then, its just simple ini edits

Share this post


Link to post
Share on other sites

I have my own ideas, but I'll leave the research to you :biggrin:

Share this post


Link to post
Share on other sites

Sabre Dog could fit...

Share this post


Link to post
Share on other sites

or the aformentioned Zipper or even the (overused) A-4E.

just need something with the CRT, maybe an RWR and windshield framing that's a fairly close match

 

personally, I think this thread belongs in the "What If..." forum ... the Hun had very much reached it's expandability potential with the D, and had always been designed as a 'clear weather' aircraft, with viturally NO night or 'all weather' capabilities. There was just no more room for growth.

 

Why do you thing the Bullpud was the most sophisticated weapon it could carry?

 

it didn't need much electronics for guidance ... just a radio transmitter and a steering stick. Adding LGBs...well, that's my opinon. Why not just use the Rhino? Got everything already in place

Share this post


Link to post
Share on other sites

Well, I've successfully used the F-101C pit and it works. Trouble is, I really want to use the F-100D pit :blink:

 

Trying to follow the instructions above, I've swapped out the clock for a small scope.

 

post-9057-0-33503900-1358645339_thumb.jpg

 

Now I've come to some more issues. Mainly,

 

1) How do I remove the hour hand. I've gone through the cockpit.ini and taken out the hands

 

Instrument[021]=TurnIndicator

Instrument[022]=

Instrument[023]=

Instrument[024]=

Instrument[025]=CautionLight

 

I have even gone as far as taking out the entries associated with them.

 

2) How do I get the radar screen to work? I've placed "RadarScope" in all three of those instrument entries along with including this at the bottom on the cockpit.ini

 

[RadarScope]

Type=RADAR_SCOPE

NodeName=Radar_Screen

 

My next move will be to create a radar folder in the cockpit folder, but dont really know how to get it to work.

Share this post


Link to post
Share on other sites

Put ClockHour, Minute, and Second back in the Instrument list.

 

Instrument[021]=TurnIndicator

Instrument[022]=ClockHour

Instrument[023]=ClockMinute

Instrument[024]=ClockSecond

Instrument[025]=CautionLight

 

Add this:

 

Instrument[055]=RadarScope

 

Then, use these entries.

 

[ClockHour]

Type=CLOCK_HOUR

NodeName=needle_clock_hour

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

 

[ClockMinute]

Type=CLOCK_MINUTE

NodeName=needle_clock_minute

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

 

[ClockSecond]

Type=CLOCK_SECOND

NodeName=needle_clock_second

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

 

[RadarScope]

Type=RADAR_SCOPE

NodeName=Clock

 

See if that works.

Edited by SupGen

Share this post


Link to post
Share on other sites

Sorry, I screwed up on the NodeNames; this should work.

 

[ClockHour]

Type=CLOCK_HOUR

NodeName=needle_clock_hr

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

 

[ClockMinute]

Type=CLOCK_MINUTE

NodeName=needle_clock_min

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

 

[ClockSecond]

Type=CLOCK_SECOND

NodeName=needle_clock_sec

MovementType=ROTATION_Z

Set[01].Position=-100.0

Set[01].Value=0.0

Set[02].Position=-99.0

Set[02].Value=1.0

Share this post


Link to post
Share on other sites

Those entries won't work...you're rotating the hands.

 

What you need to be doing is positioning the hands.

 

Use POSITION_Z instead of ROTATION_Z.

 

FC

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..