Vinc_Vega

Hi AndrewW, I did a working quick setup (only the master caution LED on D13) with the following Mega as slave and Uno as slave configs: DI -> TX0 (D1) RO -> RX0 (D0) DE/RE -> D2 So it's confirmed in principle.

Sorry my mistake, I din't count it right. So indeed force polling the trigger switch does not initiate a new counter cycle. But nevertheless, I think skipping the trigger poll is the better solution. Thank you again John for showing the coding way.

For information: the code for the A-10C battery switch trigger reads as follows and the Battery PWR Switch itselfs (eppBatteryPwr) must not be polled within the PollAllControls() function, otherwise an infinite poll cycle is created.

Hi John, thank you Sir. The changed code it is working fine. Now I have to tune my scripts a bit.

Avoid to set textsize and color within the DCS code, put it under the setup() function. Try to set first "display.setTextSize(1);" and than change size stepwise until you have the desired output. Like this: void setup() { display.begin(SSD1306_SWITCHCAPVCC, 0x3C); display.clearDisplay(); display.setTextSize(1); display.setTextColor(WHITE); DcsBios::setup(); } Than put as less as possible in your DCS code: void onUfcComm1DisplayChange(char* newValue) { /* your code here */ display.clearDisplay(); display.setCursor(35,0); display.print(newValue); display.display(); } DcsBios::StringBuffer<2> ufcComm1DisplayBuffer(0x541c, onUfcComm1DisplayChange);

Hi Blue73, I'd like to thank you too. Have used your code within my panels and they are working fine. I'm also interested in a solution that pulling is not initiated regularily. I think the idea to give a command by the BATT PWR switch is worth to try it. But my coding skills are still to poor to do it myself. Do you have an idea how to initiate pulling by a dedicated switch?

Hi Frosty, look here: [ame] [/ame] 3ds Max is really a mighty piece of software. You should do a few tutorials to learn how to use it. Here is a good one for modeling airplanes, including the texturing work: http://www.pxleyes.com/tutorial/3ds-max/2662/How-To-Model-a-Mig-29-UB-Fighter-Jet.html

Use the cross sections of your drawings for reference. Cross section "B" is in front of the canopy and rather round on top. In "C" you can see that canopy and spine are separated from the fuselage. Use a boolean modifier to cut windscreen and canopy frames.

You should model fuselage, canopy/spine and engines as separate parts. Look at the pictures below. Edit: use these drawings as backgrounds in max http://www.airwar.ru/other/draw/t38.html http://www.airwar.ru/other/draw2/t38_z.html

If you mean the green rectangular "bumb" on the top, thats just the housing of the navigation system's antenna. https://farm8.staticflickr.com/7576/15678665071_95f3688685_c.jpg Btw. all panels that have this "special green" color are antenna covers/housings (eg. nose cone and top of the fin).

As far as I know the most modifications of the Su-17M4 are implemented into the export variant (Su-22M4). Therefore no external deviations should be seen in 3D. Maybe some inlets differ (to be confirmed).

To share your progress and gather more information a new topic within the 3D section would be best. Please put a link here.

For a first glance follow that link: http://www.hat-home.de/Overview/AirForces/Germany%20-%20Laage%20-%20Home%20of%20the%20EF/slides/Badge%20of%20MFG%2028.html Btw. there were no technical differences between the navy and the bomber versions in East Germany. The TV had to be installed when operating the Ch-29T TV-guided missile (NATO Code: AS-14b), used by navy wing 28 (MFG-28 ) for anti-ship attacks. Edit: a video to see more details of East Germany's Fitters:[ame] [/ame]

Hey Frosty, Please keep us informed about your Suchoi project! And (East)German Su-22M4 hat the TVs in the Navy version too. If you need close up Cockpit pictures of the M4 and UM3K send me an email.

voted for Su-22M, the good old lady ...

Sounds like that problem: http://forums.eagle.ru/showthread.php?t=61569 I already had same issues a while ago and successfully updated to the reworked throttle firmware.

From safety point of view: first the jettison than the power switch. PS: SPRDs are working well, but booster time is to short. I read that the original was boosting for 10 to 18 seconds.

By exporting data I found out that airspeed is in m/s and has to be re-calculated for external displays. If same is for the SARPP log file, so it probatly has to be multiplied by 3,6 to get speeds in km/h.

The same happend to me when flying with afterburner for longer as ,let's say, two minutes. Maybe fuel flow is not sufficient or engine parts are protected from overheating?

Danke Lino! Hast uns einen Haufen an Arbeit erspart :-)

:thumbup: Thank you, Sir!

The prop should work in the sim cause there is arg 40 for.

Awesome +1 Tom, if you want to see 109s in RL come and visite us in ETSI.

Thank you, now it's working fine for me!

Is there any documentation how to get the (newly delivered) ModelViewer working with DCS?