-
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
Update Douglas_C-47_Beta_V3.14 feedback and support topic
- Thread starter ncooper
- Start date
Mixture again. On a testflight today I started with using manual-mixture (first time). Goodperformance on power and speed (I have made remarks on speed before, but I amhappy with this). Both mixtures are on one leaver. During the flight I changedto auto-mixture. Immediate at difference between engine#1and #2 in airflow (83<->74) and I get warning from my flysim that my engine is losing power. Speed drops with about 5 kn. Looks like for me auto-mixtureonly works correct on one engine.
Roy
Roy
banjoman1960
Charter Member
Yes Nick,these lines are for the bellylanding.......
The Betatesters request
was me....,try to do a emergencylanding .........if you do it carefull,it work now........Gooneybird565
SOH-CM-2023
@ncooper and banjoman1960
Thank you for the feed-back. Will check what happens when changing the contact point class...
Roscoe (you know, that mecanician usually proclaiming that the pilots who would damage one of his birds would endure more than hell) reminds to all of us that our aircrafts are equipped with a landing gear, and that we should use it whenever possible, otherwise
@Bjoern,
Not a specialist on that subject, but C-47 is just but the military version of the DC-3, thus few differences.
The astrodome was used for navigation with a tool most sailors did know pretty well, the sextant...
Most DC-3's and C-47 were fitted with 1200HP engines, whereas some military versions were fitted with more powerful ones (1350HP I believe).
Blue skies
Philippe
Thank you for the feed-back. Will check what happens when changing the contact point class...
Roscoe (you know, that mecanician usually proclaiming that the pilots who would damage one of his birds would endure more than hell) reminds to all of us that our aircrafts are equipped with a landing gear, and that we should use it whenever possible, otherwise
@Bjoern,
Not a specialist on that subject, but C-47 is just but the military version of the DC-3, thus few differences.
The astrodome was used for navigation with a tool most sailors did know pretty well, the sextant...
Most DC-3's and C-47 were fitted with 1200HP engines, whereas some military versions were fitted with more powerful ones (1350HP I believe).
Blue skies
Philippe
Last edited:
Yes,with one engine running at f/a 0.83 you would be losing losing power when climbing to higher altitudes.
This is a very puzzling error, so I'd be interested if it is experienced by other simmers. It didn't come up in the test phase, and I cannot replicate it.
In order to track what's happening it is important to consider the questions I asked earlier, namely,
1) Obviously, something's seriously wrong with the mixture, f/a should stand at 0.74 ... you don't have Automixture ON in General Settings by any chance, have you?
2) Since you mention "others", is this a multiplayer session? (that's one of my prime suspects as of late).
To which I'll now add:
3) In Monitor does the mixture value constantly update itself?
4) With the a/c freshly selected and on ground, try setting AR and AL without using your hardware lever, either via Monitor or the VC levers and checking the resulting f/a values?
5) In flight, try synching the engines by clicking on Monitor > Engines.
As you have noted, if all else fails you can select manual mode.
MZee1960
SOH-CM-2023
How To Get Black Leather seats in the V3.14 VC ?
Does anyone know how to do this ? I had a few VC's in the V3.12 with black seats and seatbelts, but somehow all of them are showing the seats as brown with blue seatbelts now. The VC's are fine otherwise.
I am using the 'fallback' method to point FSX to the VC repaint containing those exact 18 files and done exactly as noted here by Nick :
http://www.sim-outhouse.com/sohforu...4-released-!?p=1068881&viewfull=1#post1068881
I suspect I may have to add a new file to Nick's list to get the black seats and seatbelts as perhaps these were somehow changed/overwritten in going from V3.12 to V3.14 ?
Cheers,
MZ
Does anyone know how to do this ? I had a few VC's in the V3.12 with black seats and seatbelts, but somehow all of them are showing the seats as brown with blue seatbelts now. The VC's are fine otherwise.
I am using the 'fallback' method to point FSX to the VC repaint containing those exact 18 files and done exactly as noted here by Nick :
http://www.sim-outhouse.com/sohforu...4-released-!?p=1068881&viewfull=1#post1068881
I suspect I may have to add a new file to Nick's list to get the black seats and seatbelts as perhaps these were somehow changed/overwritten in going from V3.12 to V3.14 ?
Cheers,
MZ
MZee1960
SOH-CM-2023
Hi Nick,
No luck, I'm afraid.
No matter which route I tried, I can't get away from the brown seats with blue seatbelts. Gman's black interior file worked fine in V3.12 using the 'fallback' method. In this V3.14 it also works fine except the seats are brown and have blue seatbelts. For some reason this texture file for the brown seats with blue seatbelts seems to take precedence over anything else. All the night lighting works fine, BTW.
Here's the link to gman's black interior pics :
http://www.sim-outhouse.com/sohforu...ivery-Thread?p=1036539&viewfull=1#post1036539
Mzee I brought this up with Jan re the seat colours and this is the reason he quoted.
Yes, some VC textures needed to be changed because of the FSX bug that prevents bumpmaps to be used with the default ambient vclighting. Most important bumpmap stuff has therefore been placed on a special bitmap. It is called 'vvc_2bump.dds' and comes along with the bump and spec maps as well of course. The images for these items on the older bitmaps are therefore no longer used. They are still on the current 'vvc_1.dds' and 'vvc_4.dds' but obviously won't turn up in the V3.14 VVC anymore.
Hope this explains OUR problem and gives you an answer.I also understand the matter is however being attended.
Cheers Chris
Yes, some VC textures needed to be changed because of the FSX bug that prevents bumpmaps to be used with the default ambient vclighting. Most important bumpmap stuff has therefore been placed on a special bitmap. It is called 'vvc_2bump.dds' and comes along with the bump and spec maps as well of course. The images for these items on the older bitmaps are therefore no longer used. They are still on the current 'vvc_1.dds' and 'vvc_4.dds' but obviously won't turn up in the V3.14 VVC anymore.
Hope this explains OUR problem and gives you an answer.I also understand the matter is however being attended.
Cheers Chris
MZee1960
SOH-CM-2023
Thank-you, Chris.
Trying to figure out why I could get everything but the seats and seatbelts changed to the black configuration was beginning to drive me
and had me 
around in circles .I can now wait patiently for hopefully a new black VC compatible with the V3.14 ambient vclighting sometime in the future months, knowing this.
Cheers,
MZ
Thanks also Chris, something new to learn every day.
In the light of that, I have made a small fix.
The textures are for Gordon's texture.blackint folder only which seems to be still a popular
alternative choice.
(I suppose they could be used to add black seats to any VC)
Please find them attached.
If you want to use them, unzip the folder and place the two files from it into texture.blackint.
(The hint of brown that you see on the seat armrests is already in the blackint texture.)
However, if you are seeing blue seatbelts in the daytime, you need to review your files.
This is how Gordon's VC textures look with Jan's new vvc_2bump.dds file, this is
without the attached fix.
Not a hint of blue, which I expect is for the night lighting.
In the light of that, I have made a small fix.
The textures are for Gordon's texture.blackint folder only which seems to be still a popular
alternative choice.
(I suppose they could be used to add black seats to any VC)
Please find them attached.
If you want to use them, unzip the folder and place the two files from it into texture.blackint.
(The hint of brown that you see on the seat armrests is already in the blackint texture.)
However, if you are seeing blue seatbelts in the daytime, you need to review your files.
This is how Gordon's VC textures look with Jan's new vvc_2bump.dds file, this is
without the attached fix.
Not a hint of blue, which I expect is for the night lighting.
Last edited:
Mjahn,Thank you for taking the time. I did a test with handling the mixtures via VC levers. If I have them linked, there’s no problem.The difference in a/f occurs when I unlink the mixtures. In a normal climb, mixturesAR the a/f starts at 0.080. During the climb engine#2 stays at 0.080, the otherone slowly climbs to 0.096 at 4000 ft. After settling to cruise I am unable tomove mixture1 VC lever to AL, I have to adjust manually with hardware lever first toget it below the 0.090 and then it will move. Mixture2 is no problem. If I usemanual control of the mixtures, all works fine like V3.12. And yes I have calibratedthe mixture several times. Maybe important, I use FSUIPC for my controles.
The otheritem that not just for me, but others I fly with at DC3 Airways also is thefact that with the hardware levers we cannotget to full rights and Idle, though the engines will stop.
Roy
The otheritem that not just for me, but others I fly with at DC3 Airways also is thefact that with the hardware levers we cannotget to full rights and Idle, though the engines will stop.
Roy
With apologies for those who already are well aware of this with the intention of helping those that are not....
The texture.cfg file explained a little.
If you wish to add custom textures to an aircraft repaint, there are two choices, either
simply add the custom textures to the aircraft repaint folder or use a custom texture.cfg file
to direct the simulator to the desired files.
Both FSX and P3D look for textures first in the aircraft repaint folder referenced in the aircraft.cfg file.
If all the required textures are found there, it looks no further and displays the aircraft correctly.
In the case of multiple aircraft repaints, it can be very expensive of disk space to have all the textures
in every repaint folder, so instead it is common practice to place all the textures used by every repaint
into one folder, usually named texture.
Each repaint folder needs then only to have the textures in it that are different to all the other repaints.
However, the simulator needs to be told where the remaining textures are and this is the purpose of the
texture.cfg file.
The standard format is
[fltsim]
fallback.1=..\texture This tells the simulator to look in the texture folder inside the aircraft folder
fallback.2=..\..\..\..\Scenery\Global\texture This entry appears to make the simulator look in the simulator's main texture folder
fallback.3=..\..\..\..\..\..\Scenery\Global\texture This entry appears to make the simulator look in scenery\Global\texture
The effect is progressive, thus if all the remaining textures are found in the aircraft folder texture folder, the simulator looks no further.
If not, it will then look at the main texture folder and so on.
If, as perhaps with Gordon's texture.blackint folder, those VC textures are to be added to multiple repaints, then the texture.cfg file
will read thus
fallback.1=..\texture.blackint (Of course, the texture.blackint folder must first be added to the aircraft folder)
fallback.2=..\texture
fallback.3=..\..\..\..\Scenery\Global\texture
fallback.4=..\..\..\..\..\..\Scenery\Global\texture
and should be put into the repaint folder of any aircraft that you want to have his black VC.
The reason that it introduces Gordon's VC textures over Jan's is that the simulator looks in texture.blackint first and finds everything but the seats.
Then it looks in the aircraft texture folder and because it already has textures for Gordon's black VC, it ignores all Jan's VC textures, except the seats.
Thus the seats are displayed as brown.
It also finds all of Jan's textures that it needs for the night lighting.
Placing the two black seat textures from my post above into the texture.blackint folder stops the simulator looking for the seat textures in the
aircraft texture folder and so they display as black.
I hope that this has helped to clear up some of the misunderstandings and that you will accept it in the spirit that it is offered.
The texture.cfg file explained a little.
If you wish to add custom textures to an aircraft repaint, there are two choices, either
simply add the custom textures to the aircraft repaint folder or use a custom texture.cfg file
to direct the simulator to the desired files.
Both FSX and P3D look for textures first in the aircraft repaint folder referenced in the aircraft.cfg file.
If all the required textures are found there, it looks no further and displays the aircraft correctly.
In the case of multiple aircraft repaints, it can be very expensive of disk space to have all the textures
in every repaint folder, so instead it is common practice to place all the textures used by every repaint
into one folder, usually named texture.
Each repaint folder needs then only to have the textures in it that are different to all the other repaints.
However, the simulator needs to be told where the remaining textures are and this is the purpose of the
texture.cfg file.
The standard format is
[fltsim]
fallback.1=..\texture This tells the simulator to look in the texture folder inside the aircraft folder
fallback.2=..\..\..\..\Scenery\Global\texture This entry appears to make the simulator look in the simulator's main texture folder
fallback.3=..\..\..\..\..\..\Scenery\Global\texture This entry appears to make the simulator look in scenery\Global\texture
The effect is progressive, thus if all the remaining textures are found in the aircraft folder texture folder, the simulator looks no further.
If not, it will then look at the main texture folder and so on.
If, as perhaps with Gordon's texture.blackint folder, those VC textures are to be added to multiple repaints, then the texture.cfg file
will read thus
fallback.1=..\texture.blackint (Of course, the texture.blackint folder must first be added to the aircraft folder)
fallback.2=..\texture
fallback.3=..\..\..\..\Scenery\Global\texture
fallback.4=..\..\..\..\..\..\Scenery\Global\texture
and should be put into the repaint folder of any aircraft that you want to have his black VC.
The reason that it introduces Gordon's VC textures over Jan's is that the simulator looks in texture.blackint first and finds everything but the seats.
Then it looks in the aircraft texture folder and because it already has textures for Gordon's black VC, it ignores all Jan's VC textures, except the seats.
Thus the seats are displayed as brown.
It also finds all of Jan's textures that it needs for the night lighting.
Placing the two black seat textures from my post above into the texture.blackint folder stops the simulator looking for the seat textures in the
aircraft texture folder and so they display as black.
I hope that this has helped to clear up some of the misunderstandings and that you will accept it in the spirit that it is offered.
I fear your FSUIPC controlled hardware lever sets mixture levels that the C-47 automixture system cannot handle. Still trying to replicate your values, but so far drawing a blank. We have hardware mixture users among our beta team, but that kind of fault hasn't been reported. Perhaps check your FSUIPC mixture setup, especially for engine #1, FSX axis assignment etc.
Nick, thanks for your black seat fix for GMAN's wonderful blackint VC, together with your texture.cfg tutorial that was very helpful.
I'm not convinced that despite the methods identified to date, the blackint VC is being displayed 100% as intended in v3.14. The seats are now black and most of Gordon's VC appears to look fine, but it still does not look the same as in v3.12 from what I recall. I believe Gordon went to some length in producing various custom bumps and specs for his VC that introduced some subtle and tasteful lighting, shading and shine for certain parts of the VC. I don't appear to see these now. For example, if you look at the co-pilot seat frame and pedestal wear effects in Gordon's VC, the presentation now looks rough and pixelated (in FSX) in comparison to what I recall from v3.12 and it may well be that some of these effects are not being applied as intended in the v3.14 update.
What I did as a temporary fix until a better remedy materializes, is:
Deleted all files from Gordon's blackint folder except for the 18 files you previously identified as being necessary (panel,noseout, padding, vvc_1-11, etc).
Added your 2-file fix for the black seats.
Used the 4-line code for the texture.cfg to be placed in the individual livery folders.
While still not 100%, to my eye this looks like a more presentable compromise in getting Gordon's VC to show properly in v3.14 while smoothing out some of the rough edges noted above.
I'm loathe to suggest something like the above that alters the work and intended result of the original author, but again, as a temporary measure, this worked for me and hope the suggestion is received in the spirit intended.
I'm not convinced that despite the methods identified to date, the blackint VC is being displayed 100% as intended in v3.14. The seats are now black and most of Gordon's VC appears to look fine, but it still does not look the same as in v3.12 from what I recall. I believe Gordon went to some length in producing various custom bumps and specs for his VC that introduced some subtle and tasteful lighting, shading and shine for certain parts of the VC. I don't appear to see these now. For example, if you look at the co-pilot seat frame and pedestal wear effects in Gordon's VC, the presentation now looks rough and pixelated (in FSX) in comparison to what I recall from v3.12 and it may well be that some of these effects are not being applied as intended in the v3.14 update.
What I did as a temporary fix until a better remedy materializes, is:
Deleted all files from Gordon's blackint folder except for the 18 files you previously identified as being necessary (panel,noseout, padding, vvc_1-11, etc).
Added your 2-file fix for the black seats.
Used the 4-line code for the texture.cfg to be placed in the individual livery folders.
While still not 100%, to my eye this looks like a more presentable compromise in getting Gordon's VC to show properly in v3.14 while smoothing out some of the rough edges noted above.
I'm loathe to suggest something like the above that alters the work and intended result of the original author, but again, as a temporary measure, this worked for me and hope the suggestion is received in the spirit intended.
Bjoern
worst developer ever
Well, yes, there's little superficial difference, but still enough to question whether performance is identical or not.
Just look at the dimensions of both types on Wikipedia. The C-47 has longer span, but is shorter (cutoff tailcone for towing shackles) and weighs more (although I guess that the operational empty weight with seats and galley of a DC-3 is much in the same range).
I can't find the source of information about the wingtip extension or much more about any differences, so I'll probably have to dig up a book about the aircraft series and skim it for clues.
TeiscoDelRay
Life Time CM
Has anyone done a Chicago Southern Airlines paint for this yet? Also where can I get this updated version?
Thanks
Thanks