Leaderboard

Featuring skins by Jocko417 & myself.

Fuerza Aerea Argentina

well, A is off to the QA shop, now on to B

MiG-19SM-12P

Air Naval exercise over Aegean circa 1985

When 8 machine guns work longer than 4 cannons.

Tobruk - 1941

An old screenshot from testing something else. The chasing Hurricane skipped the repaint, and he wants his share...

you will see!

That is correct, I may alter it later on to make it A6

Polikarpov I-5P - Parani Army Air Force, 1940

After coming from my business trip to Turkey again lol (this time it is business) I will be working on the M109A2 howitzer.

Green texture completed I just need to do a one-time test to make sure everything is okay and the for upload.

McDonnell Douglas Phantom FGR.2 - No.6 squadron, RAF Near East Air Force, 1973

green light GO!! one thousand, two thousand, three thousand fo-wer, oh my lord im out the door

Hope to be alive then to put my hands on it!!!!!!!!!!!!!!!! The new MiG-17 is pure joy!!!!!!

Okay folks, this 'double cockpit' issue keeps coming up, so here's some info to help you solve your own problems. For folks who are having problems with cockpits not being in the proper position, the default is to match the entry in the data.ini: with the position in the cockpit.ini: That should in theory make your eye point from the cockpit match what the eyepoint of the pilot model, which of course should allow you to see what the pilot sees. However, TK has reduced the NearClipDistance parameter in the FLIGHTENGINE.INI in the latest patch, causing some odd issues with external aircraft parts showing that shouldn't. Lets talk a little about how all these parameters relate to each other. All Component entries in an aircraft's data.ini have this parameter: This is exactly what it sounds like...the mesh name and any SystemName in the Component entry will be visible from the cockpit view. In the FLIGHTENGINE.INI file there will be a parameter called NearClipDistance. This parameter is in meters, and tells the that within the cockpit view, anything with the distance is not to be drawn except for the cockpit LOD. Also, under normal conditions, the cockpit LOD will overdraw everything in the cockpit view (aircraft, weapon and pilot LODs). One more parameter that is sometimes relevant is the OpenCockpit parameter located in the cockpit.ini file. If this is set to TRUE, the NearClipDistance parameter will NOT be applied to that aircraft and the cockpit LOD will no longer overdraw everything. Anything with ShowFromCockpit=TRUE in the data.ini will be drawn and visible from the cockpit...even stuff that could be inside the cockpit. I use this to advantage in the F-111s, allowing you to have a WSO sitting next to you. However, all the models I have built have anticipated such a development. Note in the this OUT file: Note that the WindscreenFrame, CanopyFrame, and Cockpit are separate meshes, all the meshes normally closest to the pilot...and the ones that usually cause the visual issues. So, for this aircraft, I've put the following in the data.ini: then Note what happens...basically I've told the sim that in cockpit view, I don't want to see the Cockpit mesh (plus any submeshes) in the external model. You can do this for every mesh that you don't want to see from the cockpit view. This is the preferred method I use, to preserve the actual view from the cockpit as much as possible while avoiding clipping problems. Give that a shot for any model that you are having issues with. You may have to do some searching in the model's OUT file to determine what to hide. One additional note. If your aircraft CGPosition parameter (located in the data.ini) is anything other than 0,0,0, the method I described above will not quite work. The cockpit position will be offset by the numbers in the CGPosition parameter. The way to prevent this from happening is inserting this line into the data.ini just below the CGPostion parameter (located in the [AircraftData] section): What this does is remove the offset CGPosition and the position you set the cockpit at will be its true position reference the LOD model's zero point. In simple terms, if you always set this parameter as TRUE, the cockpit will always be put at the position you set in the cockpit.ini file. I find having this line in all my models doesn't affect anything for aircraft whose CGPosition is 0,0,0 , while fixing those aircraft who's CGPosition is something other than that. FC =========== Wrench Note: if the aircraft does NOT have the OUT supplied (which happens a lot of times), you can find the mesh name with any of the may freeware HexEditors available. All you need to know is the approximate mesh name and use the HexEditors search function to "Find" and confirm the name W

Macelena, I hope so but I don't think so. Usually, VSN mods use stock FC3 cockpits. I hope this time I am wrong.