Jump to content

Snowman

Members
  • Posts

    51
  • Joined

  • Last visited

Everything posted by Snowman

  1. Thank you 51st for the good fight today.
  2. TM Hotas Warthog + MFD Crosswind Skickat från min STF-L09 via Tapatalk
  3. Noticed this issue too but another thing that happens after the reverser has been engaged at allmost a full stop is that after disengagement of the reverser I get engine stalls when throttling up again. Skickat från min STF-L09 via Tapatalk
  4. Could also mention that the rb24 is to heavy to be carried on the outmost pylons because of stressdamage in the wings and that would significantly reduce the lifetime of the frame. Therefor the outmost pylons was only allowed to be used in times of war. Skickat från min STF-L09 via Tapatalk
  5. I have the same issue when using a axis for the radar elevation. I think it would be better if it moves without acceleration so the radar elevation stops when you stop moving the axis.
  6. I think ED dev team are trolling a bit with us here. No issues for the Viggen with this. If I would vote about this. Leave it as it is :) Skickat från min STF-L09 via Tapatalk
  7. I have a bit different experience with this. I don't have any kind of headtracker and get this pretty often with a bit of stutter to it. I have so far found out that is because of my USB-headphones. This message about plugged trackir and unplugged trackir is showing up, with a bit of stutter at the same time, every time I put the USB-charger cable into my headphones or if I turn them on or off. Also this happens randomly when I have the headphones on no matter if the USB-charging cable is plugged or not. I'm using Windows 10 Headphones are from Corsair and a USB-Wireless type.
  8. Also remember to use thr referencebutton when aligned with the runway before takeoff Skickat från min STF-L09 via Tapatalk
  9. Is there supposed to be restricted weapons for the Viggen? No bombs, BK90s or anti-ship missiles available at Vaziani.
  10. The 0-meridian is going through the Normandy map so the longitude coordinates will almost always exist in two places on the map. Example 012000E and 012000W both exist on the Normandy map. The CK37 computer doesn't have any way to tell a difference between this as far as I know. I hope Heatblur and/or ED have a solution to this. Skickat från min STF-L09 via Tapatalk
  11. Guess I'm going to increase my hours in 2.1 and blue flag in a few days then. :)
  12. Can't load up any pods or external tank for AJS37. I think the mission file is to old for the current verison.
  13. Viggens ARAK rockets would work. :D Skickat från min GT-S7275R via Tapatalk
  14. I hope I see AJS37 there as well. Skickat från min GT-S7275R via Tapatalk
  15. I have this issue as well. What for me makes this annoying is that other dcs aircrafts doesn't have this that detailed modelled. I've been thinking if this can be because of the extremly slow trim. It might be that theese blackouts happen very easy when not trimmed for the current speed. If I for example engage ATT hold when flying in mach 1.4 and the trim was done at mach 0.7 and then disengage ATT hold resulting in instant blackout. Even if I try to trim as often as I can its hard to keep the trim up because of the slow trim. Could this be the case that the blackouts are related to the trim. I did read somewhere that the trim is related to the FPS which I have a strong feeling of being true. Skickat från min GT-S7275R via Tapatalk
  16. I was flying a huey today until the server restarted at 12.35 GMT. There was serious lag on the scripts. Was several minutes between a given command in the F10 menu until there was an answer from the server. I destroyed some crates after because the server thought I was still in the air when I gave the command in CTLD. I noticed this lag in about 2hrs 15 min in mission time. After mission restarted 12.45GMT I took a huey from Malot and flew to Psebay to capture that farp. After I closed it the defenders was indestructable. I landed and dropped my troops then the server crashed instantly (about 15.05 GMT).
  17. Loadouts for Viggen There is no available external tanks or pods for AJS37 Viggen at any airfield. Could that be fixed, please? I have learned that this happens when ED realeasing a update of 1.5.x I've read somewhere on the forum that the mission file needs to be resaved to the current version. However this hasn't worked for with all my mission files. Sometimes I had to add a warehouse to the airfield with a supply chain to get it working.
  18. CTLD Hi Buddyspike-team! There is some issues with CTLD I think. I do not see any crates when I choose a AA unit or for example a repair crate. I get the answer that the crate is at my 12 o'clock but not visible. When I land to drop a crate it doesn't show up but the script is telling me that the crate is at my 12 o'clock. If it is a repair crate being used. Nothing happens. For example I captured a farp earlier tonight but the invisible crate didn't do anything to the farp as it used to be before the server was put on hold. Almost every time I have been using the huey and the CTLD the server crashes shortly after. Except earlier tonight when I actually reached a farp. One of the hueys at Saratovskays can not pick anything in the CTLD. Just get the answer that I'm not in a pickup zone. I have also noticed that if for example a farp has been destroyed and it partially repairs and then if the server has crashed before the farp is fully repaired the units at that farp have been indestructable. Might not be exactly like this but I do have encountered indestructable farp units.
  19. In the linear or logarithmically setting? Skickat från min GT-S7275R via Tapatalk
  20. Can't load any external tanks or pods on AJS 37 at in the mission "Battle for Maykop". The mission needs to be resaved in the current version or add a warehouse to the airfield. Yesterday there was no answer from groundcrew and didn't load anything at the airfields in the mission Battle for Sukhumi. However it did work for a few other airframes but not for AJS37 and another one on the red side. Don't know which though. This might have been a one time error. Guess we know next time someone reports anything from that mission when played.
×
×
  • Create New...