kemz

Hi, Here my development for simulation applications Properties: 128 buttons (24 buttons avaliable for this pcb) USB-HID interface OS independent (Linux, Win, OSX) No analog inputs yet (because of microcontroller limitation) Still in development. YouTube Fly safe...

That might be good idea for campaigns esspecially long ones. But that is BAD idea for multiplayer. Unbalanced virtual experience beetwen players will be a big problem.

Draken have interesting aero design.

Thanks for sharing.

Yes you are right about complexity. But not about challenging i think. Work principles of modern systems are more complicated but "using" these systems must be easier than the actual system working.In that way fighter pilot will have high concentration in modern battlefield and low struggling with instruments. Because of that, i think old radar, navigation, targeting or what else, data streamming... This old systems are more challenging for us. I just dont want touch screen in cockpit : )

Olders are better than newers. Because newers are easier to fly than olders. And olders are... uhmm? Ok, AMX A-11 i think. : )

Thanks for informations. So that will give a chance to ED about integrating all systems to yak-141. isnt it? : )

YAK-141 or YAK-38M would be fine. They have exotic design, vtol feature etc. But if i think about 2 seats, SU-24 will be greatfull.

I appreciated this. (Or we can use a PIC for only one indicator to decrease cost.) So a question: According to your algorihm, when delay about altitude indicator occures, will other indicators show wrong value? Or after many little delays. Maybe we couldn't notice wrong indicator because indicators (except altimeter and may be clock) are move slowly.

Sorry i just didnt notice to "RPM based problem". You can try this, if difference between visual indicator and real stepper indicator increases (lets say 5 degree), you multiply 2 to current pwm voltage. Or you run stepper motor in full voltage always. (i think 6v for standart servos and steppers) but in this case you will change your algorithm to equalization of degrees between visual and real indicators based. Or as i said, you can use gear wheel to decrease torque and increase speed : ) Regards

To solve that problem, i think you may keep the current degree of visual indicator status in global variable. I'm in if altimeter indicates 3500ft. then current degree value will be 180 degree or if altimeter=3100 ft visual indicator equals to 36 degree. a basic algo to your sketch: setupt() {} loop{ Altitude(); //take alt degre and send stepper } Altitude() { //taking visual alt codes //calculate degree of current alt (simply modular arith.) if(degree == 0) resetStepper() } resetStepper() { //set stepper indicator to 0 degree. ** } **Because you will know current degree of stepper indicator, you can reset your stepper motor. I'm in if stepper current indicator would be 3 degree your resetStepper function will backstep indicator to 3 degre (to left). Or current value equals to 358 degree. Stepper indicator will be rotated 2 degree forward (to right) by resetStepper function. And what are the properties of you stepper? You can use more sensitive stepper model. By the way i use arduno uno (i didn't remember which atmega model) but i can say that arduino is good choice comrade. Regards.

Which microcontroller you use? I didn't start to make my project but, I think: You should use subroutin that check if value close to exact value like ** (in this condition indicator of altimeter is right on 0) your stepper motor indicator goes 360 degree, same with visual indicator. According to my observation, fail ratio of real indicator is not much for one tour. Or you can split this check process for every quarter of 360 degre to reduce correction movement of real indicator. I think you tried this but if you did not, you can decrease time delay of your microcontroller to get more accurated value to indicate to steper. ** You can compute "exac value" with modular arithmetic: _exacValue = _valueOfFetchedAltitude % 100; Note that _exacValue will be approach to 0. NOT exactly 0. Because microprocessor would not be catch 0. Because of processor frequency. Regards...

+1 It is great idea! players will make more carefull moves while in operation, if they know they (if he/she survived) lose time until taken back to airfield and fly again. Damn clever! : )

+1 Turkey and Germany use F-4E model. Turkey also uses RF-4E model, but a fixed F-4E would be enough i think. Because there is no RF-4E in game : ) Woluld be nice actually...

Yes, you are right but there is a difference. Internal jammers like F/A-18 (as you said) or Mig-29S dont affect widespread (including external ECM pods in game like Sorbtsiya) and they are generally encounter againts enemy fighter aircraft radar or radar guided missiles(?). But EW aircraft like EA-6/B, EF-111 or EA-18 etc. with its EW systems, they degrades effectiveness of enemy radar systems. Im in EW aircrafts works on widespread more. If i'm wrong, warn me please. Regards Edit: I wrote this means of technical. I'm in, i just ignored any bugs about that. You know : )