• 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.

FlightSim Developers P38 Now Released

Hey folks, I got an e-mail today about the P-38 SR2 release. It finally fixed everything on the P-38 as far as I can tell, including the lights in the Red Bull bird.

BUT! Don't install it if you're also flying the FSD YF-23 -- it makes the YF-23 instruments disappear again. :gameoff:I'm sure Tim & crew will get that fixed up right away, but I'd hold off till you hear it is if you want to fly the YF-23 in the meantime.
 
Tim_FSD,

...ya mean there is a 2nd. Service Release..?!?!...

Well, I did have a list of about 8 or so items that needed some attention since Service Release # 1 came out.... :jump:

Should I re-download the whole file again or just this file above ?
 
Can't install error 910

I finally purchased because I thought all of the problems have been worked out, but I have one.

I am using Vista Ultimate 64. The download went fine just a couple of hours ago. When I try and install I get to where its trying to locate the dll.xml file but it won't allow me to select it. I get to users/name and that is as far as it allows me to select. I need to go to users/name/AppData/Roaming/Microsoft/FSX/dll. AppData/Roaming etc are not there to select. If I go to explore I have no problem.

I have done a search but can't find a solution.

Thanks,

Tom

Edit: Error 910 "No file selected" Because the install program wouldn't let me. I also had selected to run as Administrator
 
Denny,

I can't duplicate that here, but I believe you. Your files got oout of sync somehow. Download this updated file:

http://69.13.144.131/product/files/FSDevelopersYF23sr.exe

And that should take care of it. Let me know if that is not the case.
Hi Tim,

I downloaded that one and got my instruments back. However, the "License Could Not Be Validated" message came back on the Shift-F1 HUD. Before I installed the P-38 SR2 update, I had gotten rid of that. So the YF-23 SR file seems to have an older file.

I had everything working perfectly in the YF-23 and the P-38 working (except for the stuff fixed in SR2). Here's the precise sequence:

On 11/12 I re-downloaded FSDevelopersP38aps.exe (full installer) and FSDevelopersYF23.exe (full installer) and installed those. Everything was working perfectly with all instruments.

Today I installed P38SR2. That broke the instruments in the YF-23.

So at your recommendation, I downloaded the YF-23 SR again. That brought back the instruments, but also brought back the "License could not be validated" on the Shift-F1 HUD.

So I just reinstalled the 11/12 version of FSDevelopersYF23.exe on top of everything, and now the HUD message is fixed and all instruments are working again.

So, it looks like the YF23SR patch causes the HUD error, but something's different in the most recent version of the full YF-23 installer that fixes that.

Phew. All seems well now. Hope this detail helps you figure out what needs to be updated where. :)
 
O.K. I have tried too many times to get a demo going, and sent emails and downloaded "new " demo files and now I get the "you downloaded the wrong file" message..I guess it will be worth the wait?
 
Request help regarding Message 324

If someone could give me a copy of the data that the FSD P-38 enters into the DLL.XML file I could manually enter it and maybe that will solve my problem.

Thanks in advance,

Tom
 
Tim,

Thanks so much. It took me a little while to get the entries into the dll file but once I figured it out everything loaded. Took a quick test flight out of KSEA and greased the landing. Can't ask for more than that.

Thanks for the great support.:jump:

Tom
 
P-38 Update Link

Tim,

A couple things:

First, I have seen a few people here mention getting update notes via e-mail. I haven't gotten any. Did I miss something when I registered?

Taking the hint about an SR2, I went to the P-38 section on your site. I followed the links to the update, but the download button gets a "page not found" response.

Glenn
 
I do seem to have a few problems since the release of Service Release # 2. Some of these were present after Service Release #1.

... I run Vista[32], P4, 3.2GHz, 800Mhz FSB, 2Gb PC 3200 ram, 8800GT Superclocked 512 Mb, nVidia driver 190.38

... FSX / Acceleration...

... and always Preview DirectX 10... thanks for coding VC shadows many top developers do not bother with this little feature.

1. I have an anomaly with the Oxygen Cylinder Gauge in the Red Bull varaint. When I switch on the inernal VC lights... and then use the "dimmer switch" x 1 click or x 2 clicks, I lose the dial face of the Oxygen Cylinder Gauge
Oxycylpressgauge_1.png


Oxycylpressgauge_2.png


2. Does the hand operated Hydraulic pump handle in the Red Bull variant have any animation keyed to it like the other P-38s?

3. I do not have gun "Tracer effects" as seen from the VC at dusk, night, or dawn... only in day... these "tracers" can be seen at anytime in the external views.

4. It seems the VC light toggle switch between the J & L models work in an opposite fashion, but they do work.

5. I continue to have trouble with the landing light on both the J & L models... I get them then I lose them...FSX bug I guess... even reloaded different models and that does not help. The other lights show up fine no matter the time of day/night or the "viewing angle".

6. I have a concern about the "Shadin Avionics Fuel Gauge" in Red Bull, while cycling through the various modes of operation when I get to the "USED" portion I get no readout and I'm stuck there and I'm no longer able to cycle back or forward through the modes of operation.

6.a ... does the mixture controls have any effect on the fuel consumption ... GPH... as displayed by this gauge?

7. The Yippee variant has an anomaly with the exhaust radiator texture while flying early at dawn with the sun at your back... as all good pilots should
All other P-38s are okay.

Yippee_Microsoftlogo.png



8. Service Release # 1 and # 2 ...possibly the Load Manager...
have changed the aircraft cfg. file.
While I'm still able to select an aircraft at the Aircraft Selection screen at the start of FSX they are all listed as "Default" even though the thumbnails are unaffected and I'm able to select and fly the aircraft I choose.

Default.png


P-38loadmgr.png




8a. ... it seems that the ui_variation line has been altered by the Load Manager.
I thought the... title=..... line had to be unique or the aircraft would not show up in the aircraft selection window in FSX.
I guess the Load Manager can do mighty things !

FactoryFreshandui_variationentries.png



Other than these little ol' things she is fine ! :medals:
 
FlameOut, I had the same problem with the Load Manager changing the aircraft.cfg file every time it was opened. You can correct some of what shows above by going into the paint.cfg of each texture file and changing the entries to whatever you wish. It still removes the variation name leaving "" instead. I have emailed Tim about this. Waiting for an answer.
 
I do seem to have a few problems since the release of Service Release # 2. Some of these were present after Service Release #1.

... I run Vista[32], P4, 3.2GHz, 800Mhz FSB, 2Gb PC 3200 ram, 8800GT Superclocked 512 Mb, nVidia driver 190.38

... FSX / Acceleration...

... and always Preview DirectX 10... thanks for coding VC shadows many top developers do not bother with this little feature.

1. I have an anomaly with the Oxygen Cylinder Gauge in the Red Bull varaint. When I switch on the inernal VC lights... and then use the "dimmer switch" x 1 click or x 2 clicks, I lose the dial face of the Oxygen Cylinder Gauge

2. Does the hand operated Hydraulic pump handle in the Red Bull variant have any animation keyed to it like the other P-38s?

3. I do not have gun "Tracer effects" as seen from the VC at dusk, night, or dawn... only in day... these "tracers" can be seen at anytime in the external views.

4. It seems the VC light toggle switch between the J & L models work in an opposite fashion, but they do work.

5. I continue to have trouble with the landing light on both the J & L models... I get them then I lose them...FSX bug I guess... even reloaded different models and that does not help. The other lights show up fine no matter the time of day/night or the "viewing angle".

6. I have a concern about the "Shadin Avionics Fuel Gauge" in Red Bull, while cycling through the various modes of operation when I get to the "USED" portion I get no readout and I'm stuck there and I'm no longer able to cycle back or forward through the modes of operation.

6.a ... does the mixture controls have any effect on the fuel consumption ... GPH... as displayed by this gauge?

7. The Yippee variant has an anomaly with the exhaust radiator texture while flying early at dawn with the sun at your back... as all good pilots should
All other P-38s are okay.

8. Service Release # 1 and # 2 ...possibly the Load Manager...
have changed the aircraft cfg. file.
While I'm still able to select an aircraft at the Aircraft Selection screen at the start of FSX they are all listed as "Default" even though the thumbnails are unaffected and I'm able to select and fly the aircraft I choose.

8a. ... it seems that the ui_variation line has been altered by the Load Manager.
I thought the... title=..... line had to be unique or the aircraft would not show up in the aircraft selection window in FSX.
I guess the Load Manager can do mighty things !

Other than these little ol' things she is fine ! :medals:

Sorry you are having problems. Let me see if I can help.

The display and other issues you illustrate here are things we can't duplicate, or have received other reports. If you could please, run your Dirext X diagnostic and send it to us. This will give us a lot of data on your system. In case you have never done this:

Step One: Open your Windows Start menu
Step Two: In the Start Search box, type: dxdiag
Step Three: Select that program
Step Four: Press the "Save all information" button and save the output
On your hard drive
Step Five: Send us that file as an attachment to td@fsd-international.com

I will see if I can figure something out.

As far as what the load manager created in your aircraft.cfg file, it looks to me like the additional paint schemes you downloaded did not have a correctly formatted Paint.cfg file. For example, it looks like one of them just used the Paint.cfg file from the Factory Fresh paint scheme. The Load Manager uses this data to create the aircraft.cfg file. Data on how to fill out this cfg file was included in the Paint Kit instructions. You can also modify this file to display entries in the sim the way you want them.

<link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CTim%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:punctuationKerning/> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <w:DontGrowAutofit/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Verdana; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:black;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:721708891; mso-list-type:hybrid; mso-list-template-ids:-1542814632 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> The Load Manager for the P-38, located in the J model folder, uses the data in this configuration file to configure the aircraft the way you want it in the simulator. You can specify:
<o:p> </o:p>

  • The title in the simulator. This is used for both creating save Flights, and also, will specify the variation name as it will appear in the simulator Select Aircraft menu. The first line in the Paint.cfg file, ‘title=’ in where you put this text. For example, title=P38L Black Knight.
  • The model file to be used. In cases where you want the P38J to use the more modern restored cockpit you can specify this by making this line model=Restored. This will be written to the aircraft.cfg file and the plane with your paint scheme will load using that cockpit.
  • The panel file to be used works the same way, so if you want to use the modern cockpit with your paint scheme you must also specify panel=Restored here.
  • The ATC ID you wish Flight Simulator to use can also be specified. If you want to be ID N27FE enter atc_id= N27FE.
<o:p> </o:p>
*Note that the restored model and panel are only for use with the J model.
 
Tim, as posted above, I have changed all my paint.cfgs carefully but still have the variation showing up with 2 quotation marks. ("") Help.
 
Tim_FSD,


... will do... it's been very busy around the homestead today and will be late tomorrow at work.
Then I'll get on it ASAP. :running:
 
Back
Top