Maraudeur

Roger that :thumbup: Thanks for your consideration and your spent time :smilewink:

I vas thinking about this thread: http://forums.eagle.ru/showpost.php?p=1616157&postcount=566 Ok, so my mistake for the AI aircraft, I though this could have been also a issue for this thread for it occured as well on flyable and non flyable aircrafts , but indeed when lately activated. I was quite sure that it was also possible to late activate an aircraft intended to be flown by a multiplayer client. I'm sorry but I was a bit upset to see no comment about theses bugs. Maybe the one with the US landing lights is OK? (see the A-10 and UH1-H on the track) Anyway, happy to see that your're still serioulsy and accurately monitoring this forum, I'll keep continuing to track the bugs. By the way I'll also make a report of bugs in the list that are redundent. Thanks for your attention. :thumbup:

So I should consider the bugs I reported previously (on screeshots and trk) are not taken in account? :huh: So far I think I'll save my time just waiting for a miracle :cry: I was quite sure that an issue such as missing ejection seats on IA aicrafts waiting to be activated was aserious one, obviously not :music_whistling:

:music_whistling:Yes indeed, no sidewinder warning for launch, my mistake, but also no radar emission warning on my SPO despite I was in the Hawk detection area:no_sad:

Ok, take this track Viper! :lol: Multitrack Track.trk Ok this you will find: - flaps noises "bouncing" at the end (played twice pitched) - ejection seats missing in the A-10 lately activated (uncontrolled then switch activated 60s later) - UH-1H strangely belonging to Russian side (with National Guard skin :music_whistling:) an displaying an horrible landing light halo cone - Leader of the A-10 flight switching off the nav lights beut all the three wingies keeping their flashing - stealth SU-27 approach and kill (R-73 + canon) but still no warning on the SPÖ for any lock and AIM-9 launch...then seeing my defeat :cry: Enjoy and let me know. FC3-DCS version is the last one 7570 :smilewink:

Roger that! Thanks a lot

Sorry, no track for the moment as I performed the test on an other machine than the one I'm posting from.:huh: Anyway, my version is 1.2.2.7286 :thumbup: By the way, it seems that there are new updates? Such as 7570? Why can't I update to this version via the automatic updater?

I also forgot these: 1- Client players not seeing the hangar doors opening for other players 2- Awfull sideview of the laxy lights on US a/c (with cone too much marked and visible) 3- Also still complaining about the weird textures in the SU-27 mirrors (is the cleanig staff still on strike?)

Here are some other bugs: 1- When setting F-15 non controlled on the ramps and making a startup afterwards by AI-switch - Start, there is indeed no pilot in the canopy as long as the switch is no activated, but amazingly there is also NO ejection seat in de cockpit. Do the pilots come with their own MK-10??? (I noticed this with the F-15, haven't performed the same tast with other planes yet) 2- Strange illumination of the pilot coming from the back of the seat, but only on the #2 to #4, not on the leader. As well as the wingmen keep their navlights and formation lights on on the contrary of the leader. Bug discovered on a flight of 4 AI A-10, not yet tested with other aircrafts.

Nice job anyway! Could you please also have a look at the green autopilot indicator leds that are displaced (i mean too much right from where they should be) on the SU-27 Thanks.

- Bug at startup on IA SU-25T: we can ear an aibrake out/in noise at the very firts momentn of the startup, but with no visible motion from F2 point of view. - F-10 bug with the SU-27 (not tested with other aircrafts): maps always switches back ON the MGRS grid each time you come back to F-10 view, no matter what you preset previously - wind drift has NO effect on the chaff/flare thus it does on parachutes and vehicules dust trail - dust tail occurs far lower than previously (same as for the overwater effect) - SU-27 mirrors present weird textures (ans also seems over dimmensionned)

ILS bugs in FC3 Here is a short summup of ILS bugs detected in FC3 with my SU-27. Let me know if you wish me to complete the test or if I can save my efforts to help :smilewink: Also be aware of the fact that I lead a SU-27 virtual squadron (the 92nd Kodiak AF) and that we may help by performing multiple tests and/or bug chase to help ED to track and solve ASAP the bugs :thumbup: ILS in FC3.pdf

This documentation should give you the correct fuel management for the SU-27 :thumbup: Just use the google tranlator to set it in rough english. Wishing you a good reading; Do not hesitate to contact me for further informations ;) Su-27Book2Russian.pdf

Also noticed the small dashes on the HUD but in up right position. For the IAS on final, firts make sure zto have exactly the same configuration (air T°, loadout, fuel remaining) to be able to make a goog comparision) for the IAS on the HUD is only the prescribed speed @ touchdown (V POS) that is conputed in accordance with above parameters. Russain pilots do not use a constant VRF to fly the final track. The speed constantly decrease by 10km/h per km flown on final to meet the Vpos at touchdown.

+1 makes 101% ;-)

Thank you so much! I couldn't enven stand anymore the blue "eastern" color ;-) And do you have any solution for the awfull textures in the mirrors?

I'd never thank you enough for all the job you did since the very first LockOn. I'll surely by the new FC3 for it will enable our members of the 3rd Wing to all fly together again (that is the back bone of the simulation). I perfectly understand that it takes time to make improvements in that "game", but I feel forgotten by you "creators" as all the new improvements since DCS seems to come to the eastern fixed wings aircrafts. As there is no plan to release an other FC version, do you think about releasing improvements in the eatern aircrafts (such as a niiiiice cockpit) as beeing "free" patches for FC 3?:cry: Just to help us to wait for a nice "real" DCS eastern release :music_whistling:

Ok for the "new" AFM of the missiles (and rockets?), but will the fu****g bug of the SPO be fixed enough? I mean no launch warning with many aircrafts (I think in particular of the F-4. It's nice to have better missiles if we also have a correct SPO...

Oups! My mistake :music_whistling: Indeed, I just mixed you up :cry: Anyway, I so send the same question to wasserfall :smartass:

@JoeKurr: this activity in this topic just made me more impatient to build my cockpit SU-27 MK2 ;-) Would you be kind enough to send me your "blueprints" (just for panel size purposes, not to make a copy of your so nice work), as you may have seen on my photos, my pit #1 was obviously too narrow! I'd like to start building my different panel, starting by the chaf/flare dispenser and then the SPO/ECM panel

Yes, indeed, the sioc variables are linked to whatever you want: a switch, a rotactor, a led, an analogic entry (up to 4 on the USB expansion card that return a value between 0-255), a LCD display, and so on. You can also define local variable that are used to count some values, make some basic operation on them, or use them as a flag. ON THE REAL su-27 the selector is a cotactor with some discrete values, just look there http://server.3rd-wing.net/public/Maraudeur/Chaff%20and%20IR%20decoy%20dispensing%20device%20APP-50.doc this is the reason why i used a 12 position rotactor. A swtich changing its position from opened to closed will change the value of the assiociated variable from 0 to 1, but only when the siwtch changes its satus (meaning that a switch continuously closed will not contiuously send a 1; this is just its related variable that changes its value) As for an example, if I set the gear lever UP before taking off, it won't move, even when airborne. To have the gear retractiong I must set the lever back DOWN, then UP, to have the command returning 0 and then sending the order to LockOn Its funnig that you pointed out the variable V0999, because this one is the one used to send informations to the LUA, and thus to LockOn. A friend of mine (Lecreole) choose to make the LUA calculate everything, but it lead to a slowdown while the export.lua was used for Lotact+Lovp+Lomod and so on... This is the reason why he reverted on my solution to make the lua calculate the basic values, but let the SIOC deal with these values. But nevertheless we need to have informations about the actual status of the different devices of the SU-27 (position of the flaps, gear legs, airbrake, trims values, hydraulic value, canopy position, and so on)

@JoeKurr: As an example, here is my SIOC routine for the fuel tanks level indicators: Var 1025, Link IOCP, Offset 0, Value 0 // Fuel internal (KG) { IF V1025 > 8400 { &8400_ind = 0 &5200_ind = 0 &4300_ind = 0 &150_ind = 0 &500_ind = 0 } ELSE { IF V1025 > 5200 { &8400_ind = 1 &5200_ind = 0 &4300_ind = 0 &150_ind = 0 &500_ind = 0 } ELSE { IF V1025 > 4300 { &8400_ind = 1 &5200_ind = 1 &4300_ind = 0 &150_ind = 0 &500_ind = 0 } ELSE { IF V1025 > 500 { &8400_ind = 1 &5200_ind = 1 &4300_ind = 1 &150_ind = 0 &500_ind = 0 } ELSE { IF V1025 > 150 { &8400_ind = 1 &5200_ind = 1 &4300_ind = 1 &150_ind = 0 &500_ind = 1 } ELSE { &8400_ind = 1 &5200_ind = 1 &4300_ind = 1 &150_ind = 1 &500_ind = 1 } } } } } } Here is my Emergency payload jettison: Var 0303, name Emer_jett, Link IOCARD_SW, Input 3 // Emergency jettison { IF &Emer_jett = 1 { V0999 = DELAY 529 ,10 V0999 = DELAY 529 ,20 V0999 = DELAY 529 ,30 V0999 = DELAY 529 ,40 V0999 = DELAY 529 ,50 } } The landing gear routine with the indicators: Var 0313, name Gear, Link IOCARD_SW, Input 13 // Gear Handle { IF &Gear = 0 // Gear handle UP { &Gear_Fail_ind = 1 &Gear_ind = 0 &Gear_Fail_ind = DELAY 0 ,700 V0999 = 546 } ELSE // Gear handle DOWN { IF &IAS < 500 { IF V1043 = 1 // If gear U/S { &Gear_Fail_ind = 1 } ELSE // If Gear is OK { &Gear_Fail_ind = 1 &BlinkLed = 10 &BlinkLed = TIMER 0 ,-1 ,50 &Gear_ind = DELAY 1 ,600 &Flaps_ind = DELAY 1 ,600 &Gear_Fail_ind = DELAY 0 ,600 V0999 = 32802 } } } } And the small routine to make the leds blink: Var 0100, name BlinkLed { L0 = MOD &BlinkLed ,2 IF L0 = 0 { &Flaps_ind = 0 } ELSE { &Flaps_ind = 1 } }

Fot your information Sov13t, a rough tranlation of the Chaff and Flares control panel, I left this one just as it, for I translated the "nicest" one in french... You'll find it there: http://server.3rd-wing.net/public/Maraudeur/Chaff%20and%20IR%20decoy%20dispensing%20device%20APP-50.doc

Yes, I've managed to understand a big amount of the russian acronymous in the cockpit, nearly the totality of the ones used in FC2, and many others, in particular for specific panels such as the chaff/decoy, the ECM, etc... I also have succeeded in understanding the way it works in the real a/c to be able to emulate it in my cockpit. Just send a snapshot of the acronymous you want to identify, and I'll explain it to you (as far as I can...) @JoeKurr: I'm still wondering why you need an alog 10-bit for that panel. Using SIOC and its language I completely manage the Chaff panel, including the LEDs bar displays. For my gear and flaps panel, it's already managed by the SIOC; I mean that the indicators only depend on the switches position, by I use dirrerent tests (such as the IAS<500km/h, the hyd pressure, etc) to make sure the lights will be in accordance with the panel in FC2. A SIOC only reacts to state changings (0 or 1) the gear won't extend if I initialize in flight with my pit gear handle down :smilewink:)

@Edrom: as far as I've understood the changelog, the new version of SIOC (4.0) include spécial network procedures that may solve your problem: "The new version implements an special communications protocol via UDP, that allows the remote control of all electronic cards connected to any SIOC in the same network." @Joe Kurr: that's an other great new to be able to get the hydraulic pressure values! It means that I would be able to make a functionnal HYD PRESS indicator, and to manage the failures (as long as I want to complicate my life with failures not taken in account in FC2 ;-)) I do have already a working routine for the SIOC to make the indicators Blink, if your're interested in!... For the gear, I though that: "gear = {status,value,main = {left = {rod},right = {rod},nose = {rod}}}" returned the individual states of each landing leg (in case of partial extension of the landing gear)