Jump to content

Bassly

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by Bassly

  1. Well landing flaps are on the V350, but at the moment you can use the flaps with the battery only connected without the V350 in. To both directions and in all positions. So no, does not make much sense. It was internally fixed two updates ago, but it's not added yet I guess?
  2. That's probably, because you need two fuses E16 and V24 to operate the landing gear properly. E16 is the electric motor main circuit, V24 is the electric motor control circuit and the V24 most likely contains the gear locks too. As an example: Lets say you are flying and have landing gear up. E16 is out and V24 is ok. You press landing gear down, gear locks release and gravity does the rest. Then you want the landing gear back up, but since you don't have electric motor main circuit working, landing gear stays down. Next case would be V24 out and E16 ok, flying and landing gear up. Nothing happens, because the gear locks wont release and the electric motor won't get the actual control command when or which way to spin. So, without control circuit the electric motor is just sitting there, doing nothing. The diagram ED provided with manual is very basic, but does the job. By the looks they even thought about the landing gear extension with motor and motorless. Without the motor landing gear extend much faster than with the motor, just like when using the emergency handle. Another nice little detail there. :thumbup:
  3. I did first the cold start to 10km too and since there was no actual difference I did the airstart for the track. But the fact that I'm doing something that should be done only in emergency situations works better than normal operation... Without any damage indicated. Hard to say. Althought everything is done within the values given in the manual. Max. M2.05, setting for manual nosecone 40%, which was given for the mach >1.8. It was 40%, not >40%. Likewise it would be interesting to hear a some sort of "yes/no" on the matter.
  4. True, there's not much room for error indeed. In the end I found EGT more accurate to adjust the speed instead of the RPM gauge. You'll just need to be soft on the throttle. More important thing was the nosecone control. There's are values for each mach range for the manual nosecone control in the manual page 59. For some reason the auto nosecone control goes well beyond the 40% at speeds over M1.8 and makes it harder to control the throttle and keep the speed steady. Eventually you'll just cut your engine. I pretty much just followed the table values and instructions how to manually operate the nosecone. I rolled the empty needle to 40%, kept the nosecone on auto until the needles matched each other at M1.8 and flipped nosecone to manual. When I was nearing M2.0 I started to drop throttle and follow the EGT vs. M/IAS. That's how I got more room to adjust the speed for the M2.05. Is this how it is supposed to be operated... that I cannot answer.
  5. Here's a solid M2.05 run at 10000m till the tanks are empty. Edit: SARPP file says January, but it's one to one record with track from today Feb. M2.05_run.trk SARPP_DATA_2015_01_28_19_31.txt
  6. Oh yeah. That's a very important thing to take into account when using the radar. Don't mind too much on the red circle, I just threw it somewhere on the dashboard and tapped on the manual. All yours.
  7. No science here, but I did set a test mission with one Su-27 flying 900km/h directly towards me on various altitudes. Right after mission start I set myself into active pause and let the Su-27 fly on my radar. Lines are not dead accurate, but the results were well... For the last a random picture from multiplayer of a player F-15C, no one else over there. My nose was pointing ahead of him whole climb. Got only a T. Kept pushing nose down for inverted T, no hope. Angle looks bit extreme because of the delay I guess. It went blank on the next scan. Only thing I can do right now is scratch my head and throw my eyes out of the window. In manual I believe. :book:
  8. I tried to search for any kind of correction on the radar target position indicators and found nothing. So, is the manual correct on the: Inverted T sign = Target above you. Combined inverted and T sign = Target on your level. T sign = Target below you. I'm getting quite opposite results between above and below. Is it the manual or the radar that is misleading here?
  9. True, been there a while and for the rest we'll just have to wait patient. I just don't see the reason why someone would put aircraft on their official page when they have nothing to do with them. /end of speculation.
  10. There's a butterfly screw below the pipe and the pipe is cut where the screw is. So you just plug the gun into position where you want it to be. Then tighten the screw, the gap gets thinner and squeezes the flare gun to seal it. If it would be permanently in flight removable, there would an instrument to plug the hole, but haven't seen one yet in this thread. Data sheets, go. I would prefer the ground crew method, but mission editor way goes fine too.
  11. Update 1.2.14.35734.604 and the new engine sounds. When having the afterburner and 100% RPM "maximal" engine nozzle control switch (LV33) set to down position and controller throttle axis beyond the limit that the LV33 sets for logical axis (physical axis over the 101% point for the low pressure compressor), the non afb. engine high pitch sound starts to cutting off and on. When you return the controller axis to match the 101% logical axis for low pressure compressor the sound returns stable. Or when physical axis is tiny bit over the logical axis of the 101% for low pressure compressor and you set LV33 switch to up position, the cutting sound changes to afterburner sounds. Other than that, the new sounds are great. :thumbup:
  12. For some reason the generator cuts off above around 1500-1600rpm, so you are basicly flying on the battery above that. And the stuff you can do without both battery and generator while flying is quite nice... Or without any other electrical system. I would dare to assume that the electrical system is still pretty much wip. With radio usage it's the same. Turn your battery off, call ATC below 1600rpm, it works. Go above 1600rpm it doesn't, keep the above 1600rpm support with battery, ATC responds. So, if you use radio above the 1600rpm you are using your battery I guess.
  13. I guess the aircraft are flying so slow, that without low speed filter they wont show on the radar. Also since they are flying so low too, you could compensate the clutter with the RV64 switch next to the RV62 main radar switch. Otherwise the mission works fine for me.
  14. When using default keybinding for Radar Interferes - Weather (Radar ECM protection panel - Weather, LShift + R), the whole mission resets. You can bind it to some other keys, but the mission reset remains on the LShift + R and there is no slot for it in the key options while using the module. Mission restart can be found in the launcher options under "General" Aircraft drop menu, but unbinding it doesn't fix the issue either. For MP the keybinding does not work at all. Just a small observation.
  15. A little tip I would give. When you create advanced commands in SST, it's very important to have a "key release" for each executed "key press". Otherwise you will end up keys pressed down until they get the release command elsewhere. Like now, if you use your slew left and then right, you will have the slew left down when operating on slew right zone and both down when returning middle. So instead, I would set it like this: Difference is that when you operate on the 20% Mouse X Axis zone, it holds the dot down and when you leave the 20% Mouse X Axis zone ie. return to middle, it sends a dot release key command. That's how you avoid all the ghost presses etc. And by right clicking on each press/release column and selecting "Quantize Time" to 0,000 you can get rid of the delays you created. In some cases you need a little delay, but in this most likely not. Otherwise it's a nice guide. Happy nipple rubbing!
  16. http://www.digitalcombatsimulator.com/en/faq/activation_wiki/ There are links for each module at the bottom page. Download the correct file and run it. Then run DCS, play with MiG and it should ask you to activate it. If it doesn't hold shift and launch multiplayer from desktop.
  17. First making it realistic way and then giving a simplified option would make completely sense, but this way around. I don't even... So yes, realistic steering/braking pretty please. (Insert stereotypical "Fix it now/I want it now" here.)
  18. My top score would be 108x13mm and 52x20mm hits. Then, I also get results like these: Wouldn't say that cannons are too weak, but something else is bit off. Working as should be working? No. So I guess time is the one what is needed here. One can wish.
  19. To add here. When you restart your current mission with LShift+R (Restart Mission), the airbrake sound will be missing on the first airbrake open/close. On the second airbrake open the sound will cut in at its loudest point and then behave normally. I have airbrake binded on single button Joy31 (Airbrake). Lets say you take the free flight quick mission, fly around and then hit LShift+R. That's how you should get the situation described above.
  20. This... just amazing! :music_whistling:
  21. No, some side project with RMHS I guess.
  22. Dear Santa. DCS Mig-21BIS, pretty please.
  23. I really hope they would give a second go and allow to donate for the project later on.
×
×
  • Create New...