Captain Orso

Firstly, you have to understand that the scene only deals with objects in a very rudimentary sense. The P-47 might as well be a shoebox as far as the scene rederer is concerned. It doesn't consider gravity, nor facing, nothing. The Scene uses cartesian geometry, but not degrees. You will have to try values and observer effects. For my description, let's assume the X axis goes left-right, the Y axis goes up-down, and the Z axis goes toward-away from you. This line is from your scene file: scene.m = sceneAPI:addModel("P-47D", 5, 2.3, -4); The parameters 5, 2.3, and -4 deal with the position of the P-47 within the scene, so 5 in one directions, 2.3 in another, and -4 in the third - that is how you control the position of the P-47 in your scene. You can also control the attitude of the P-47 using scene.m.transform:setOrient(0, 0, 0); Each parameter rolls the P-47 along either the X, Y, or Z axis. So to get the tail to rest on the ground you will have to find the which parameter rotates the P-47 around the axis coinciding with the wings, but this will probably also raise the main wheels while the tail wheel goes down, because the scene renderer is only concerned with the geometrical center of the object. Therefore you will have to adjust "scene.m = sceneAPI:addModel("P-47D", 5, 2.3, -4);" to put the wheels on the ground again. If you want the P-47 to be at an angle in relation to the "front" of the scene, you will have to change the sceneAPI parameters to turn the P-47 around the Y axis. But this will not hold the nose (already pointing above the horizontal) at the same angle - we are only concerned with geometry, not physics. So if you bring the nose up 15° and then spin the airframe 90 clockwise, instead of the nose pointing 15° above the horizon, now the left wingtip is point 15° above the horizon, so you will have to change the "scene.m.transform:setOrient(0, 0, 0);" parameters to fix this. If you want to have the P-47 at a diagonal... you will have to play with the parameters a freaking long time to get them right. I know, I did it will the P-51 My P-51 Scene Look through the posts from back then, I talked a lot about this stuff (mostly begging for answers) back then. BTW If you want to have more than one aircraft in the scene, do this: scene.m1 = sceneAPI:addModel("P-51D-25-NA", 15, 1.9, 6); Enumerate each aircraft or object after the "m"; eg m1, m2, m3, etc. Good luck, and don't get to frustrated. You'll get there eventually.

There are two plunger/buttons behind the pilot's seat for cutting off the engines. The mixture lever only has Rich and Lean, no cutoff.

Are you using VR?

Many thanks for the reply. I was just wondering why other aircraft enter it for you. After all, if the target is at 900 feet altitude and you don't enter it, leaving it at 0, if you use the waypoint as a TGT, nothing will ever hit, because everything will be aiming for 900 feet below ground level.

Hi all you aces. I don't fly the F-16 - yet - but I have a kind of a survey question. When you enter a waypoint, either through LatLong or MGRS entry, once the LatLong or MGRS has been entered, is the ground level elevation of the waypoint already entered for you, or do you have to reference it from somewhere and enter it manually in addition and subsequent to the LatLong or MGRS coordinates? Many t(h)anks in advance

Of course I tried setting the HPTP first, as noted in my first post. As soon as the R/BL mode is selected, HPTP disappears from the options.

Thanks for the reply! I know that it is a bug that you have to make a waypoint your steer point and then designate as target for the B/RL option to appear under Mode, but what I'd read elsewhere in the forums, it sounded like it worked otherwise. I guess it's off to the bugs section.

I'm guessing, you want to create a customer kneeboard for the Mosquito using one or more JPG files. Principally, it should work, but KBB seems to have some kind of bug preventing it. For me KBB crashes every time I try to create a new group for the Mosquito. The way it should work for importing image files directly, is: -> select "Create Custom Kneeboard" -> select the aircraft -> at the bottom of the left window (available groups) click [New] -> Name the group -> select the newly created group -> click on [Modify] -> at the bottom left of the window click [Import Images] -> select the images you wish through the Windows dialog window. But, as I stated, for MosquitoFBMkVI KBB crashes when I try to create a new group. You could simply add the images directly to the Mossy kneeboard location, if you wish. Just put them into c:\Users\your_user_name\Saved Games\DCS.openbeta\Kneeboard\MosquitoFBMkVI\ and place the JPG files there. The file names should follow the following scheme: xxxx-Aaaaaaaaa-nnnn where xxxx is a 4 digit number, starting with 0001 enumerating the kneeboard group name for sorting purposes. xxxx should increase by 1 per group. Aaaaa is an alpha-numeric string which may include space characters being the actual name of the kneeboard group. nnnn is a 4 digit number, starting with 0001 denoting the position of the file within the group for sorting purposes. nnnn should increase by 1 per file within a group. The next group starts with 0001 again. EG: 001-A10C StartUp Checklist Day per ralfidude by Capt Orso-000.png 001-A10C StartUp Checklist Day per ralfidude by Capt Orso-001.png 001-A10C StartUp Checklist Day per ralfidude by Capt Orso-002.png 002-A10C_2 HOTAS Charts Day by Capt Orso-000.png 002-A10C_2 HOTAS Charts Day by Capt Orso-001.png 003-RWR Charts Day_copy-001.png Hope this helps.

2 days and over 100 views, and not a single tip or remark

Yes, this ol' beast again. Short Question: How do I use HPTP in B/RL mode? -- If I don't select the Target WP and Designated to TGT, I cannot select B/RL in the PROG mode. -- If I want to use the HPTP (which I do) I have to set the Turn WP to the Steer Point, and then press the OSB next to HPTP to box it. But as soon as I switch the Waypoint to the Turn Waypoint, the PROG mode changes to BOL(!!). -- If I set the HPTP first, as soon as I change the mode to B/RL, the HPTP status disappears, and I'm back at square one. This is Catch-22! How is this supposed to work?

Logbook entries: Pilot: After losing both wings, propellers still present. Crew chief: Don't lose wings.

Thanks for the replies. I hope they publish some limits on which to orient.

What?! I didn't realize the Mossie doesn't have one. I'm just learning the Mossie and didn't realize it's not there. But I until I've looked behind the pilot's seat and under the wings, I'm not going to unequivocally state that there isn't one Don't ask me how long I looked for the fuel cocks before finding them, because you don't want to known... it was at least an hour

You don't. The airframe is at an angle so you cannot put the wings indicators on the artificial horizon. You also don't have to. If after take off you want to the the AH as close to perfect as possible you need to observer the vertical speed indicator (shows your rate of climb/descent), the yaw or slip indicator, and the turn or roll indicator. These instruments work on the inertial forces on the aircraft and if you are flying absolutely level and straight and true to flight direction, they will all be centered. Then you can cage and uncage the AH and it will be perfectly set. Note however, that the AH is attached to a set of gyroscopes, which true to physics will tend to wander off their true indication after experiencing prolonged and extensive forces - if you circle and airfield, after the first 180° turn you may already see the AH being off 5° or so. If you fly straight and level for awhile this will correct itself, or you can do as above again. If you have gone through any strong turns - like in combat - don't count on the AH being correct. ChecK V/S and Slip indicators if you are in a cloud or can otherwise not observe the horizon.

Thanks for the replies, guys. Are those given operational limits, or simply that the engines won't run at higher RPM's because there is simply less fuel being fed to them?

The manual states that it's there, but not how to use it. Per default it is set to Rich (lower position) and there is no Cut-Off position (Cut-off is per plunger-press per engine behind the pilot's seat) and the upper position is Lean. The is no problem to starting the engines without touching the Fuel Mixture lever, and I've not read anything to the contrary. I believe I read something on a checklist that you can set to lean for optimal long-range cruising, but there's nothing in the manual. So how am I to use the Fuel Mixture lever?

Am I losing my mind or did the Controller settings "Chassis Lever ..." just get changed to "Undercarriage gear ..." in the DCS 2.7.6.13133 Open Beta update yesterday, 22-Sep?

In-cockpit there are levers with an upward, centered, and downward positions. I have switches on my HOTAS with upward, centered, and downward positions. This is exactly like the F/A-18C's so-called 'Special For Joystick' binds for the flaps; basically two simple On/Off switch binds with the middle position being the unasserted position for each bind, which corresponds exactly to a three-way (On/Off/On) switch. These are simple things which have already been done many times in other modules. This should be no issue to fix.

Thanks for the reply. At any rate, all the information the IFFCC and EGI contain were deemed to be insufficient to make a useful calculation for deploying the CBU-97 without adding a unit to dynamically calculate and control the fall of the weapon, and this compensation is only useful if it also considers the deployment of the BLUs, otherwise the expensive development and deployment of the WCMD would be pointless. See my immediately previous post (video).

The LASTE page shows the waypoint information. The STRINFO shows the steerpoint information. The wind info on those pages are entered and not calculated. If your target is not near a waypoint, you will have no wind information. If your target is in a valley and far enough from a waypoint that the waypoint is not within the valley, nothing in your closest waypoint wind information will be of any use other than coincidentally. Now imagine there are gusts in addition. The WCMD only makes sense if it is compensating not only the fall direction in wind, but also the drift of the BLU-108s while on their parachutes. The effect of wind on the canister is low, because of the weight of the canister (inertia) and its form. A 15,000 foot fall takes 30 seconds. Once the canister deploys (default = 2200 feet above target altitude) the BLU-108s are on parachutes. The BLU-108s are far lighter than the entire canister, plus they are hanging on parachute. The entire concept of a parachute is to increase as greatly as possible the force necessary to move an object through the atmosphere. conversely, wind (movement of the atmosphere over the earth) is equally great. After deployment the first BLU-108 fires at about 17 seconds and the last at about 27 seconds. During this time while hanging on their parachutes, the BLU-108s are blown off target a great distance. With 25 kts wind speed on the ground at the point of deployment, the BLUs drift so far that not a single skeet touches on of the target vehicles in the convoy (see video). If the WCMD does not compensate for the BLU-108's drift while on parachute, it is useless. DCS CBU-105 from 16k+

I've been talking about both. On the one side, arguing that the way it currently works in DCS, can't be the way it works in Real-Life™. Then explaining my experiences in using WCMD's in DCS. No, I'm talking about the IFFCC (Integrated Flight & Fire Control Computer). EGI (Embedded GPS & Inertial Navigation System) is for navigation. If you think EGI is calculating wind speed and direction, then it must be storing the results, and it must be viewable. I'd surely like to know how to look at this information. If you think anything you can discern from measuring your flight heading deviation will be anywhere near close enough to accurately drop a bomb on target from 15,000 feet, I think you have a very vivid fantasy.

Go drop an WCMD in winds and report the results. I'm tired of trying to spoon feed those resistant to evidence.

This thread is about the Litening II Targeting Pod and not the IR-Mavs. The quality of the TGP's CCD feed doesn't even come close to the ancient Zenith BW TV I watched as a kid in the 60's. The contrast is almost non-existent; it's just a green-gray garble of splotchy nothing. The only time I ever use it is if the targets are on a road or parking lot in bright sunlight. Otherwise I almost only ever use IR with Black-Hot.

Oh really. And how does the board computer know the direction the wind is blowing and the strength? If CCIP/CCRP already did it all, there would be no requirement for an extremely expensive WCMD, would there.

That was the whole point of my wish that ED brings the Huey up-to-date with the other modules that emulate this function perfectly.