Jump to content

FZG_Immel

Members
  • Posts

    1794
  • Joined

  • Last visited

  • Days Won

    4

2 Followers

Personal Information

  • Flight Simulators
    DCS, Il2BOS&CO, BMS
  • Location
    Switzerland
  • Interests
    Flying, Flight sim, guns, shooting

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. after 90min on contention Cold War server tonight.. All cores where throttled at least once. dcs.log
  2. forget about my sign. this was before my intel CPU died 1 year ago. I am now running the Intel safe BIOS and settings, since they clearly have issuee with gen13/14 CPUs
  3. I confirm this happening with Intel, non OC. 13900k here. I have a 14900k sitting in a box in case this one burns away. Yes yes. don't worry. My old CPU intel died because of this about a year ago. It's been replaced by intel, and I am now running it with latest BIOS and safe setting (at a loss of performance of course). I even have a 14900k that is sitting on the side that I bought until my 13900k would be replaced. Clearly there is an issue with the latest patch. never had such high temps since I updated the BIOS with the new intel 'safe' settings I have no log to report, as I have no crash myself. just very high temps
  4. please go read the dedicated thread i linked.. Most people have this. Plenty documented I dont want to run DCS until it pushes my CPU at 100°.
  5. that aint serious (that was just loading Cold War Contention server. not even going 3d) :
  6. read my edit of the post before.. we had peak at 100° and average at 95°....
  7. friend had 3 freezes and blue screen tonight after the patch. prolly temp linked too. myself my CPU had peaks at freaking 100° !!!! and was idle in the mid 90°s I dont want to burn another intel CPU... Not playing DCS tonight anymore. Come on ED; this is not serious
  8. the pilot clicking allow control ? Sometimes some quick reaction is needed and this is a problem. I understand the option needs to exist for when you are online with randoms, but in the mirage F1 you can select this as an option
  9. I believe i simpy turn the intensity down
  10. Well... I can't explain why, but after 2 flights, everything works as usual. I am puzzled. Sorry for the trouble.
  11. Thanks for the quick feedback. if I hit the cage button, to enter the flood, and then I select the proper aspect ( via WSO jester keybeind ) and launch my sparrow within parameters, it never tracks.. if I enter hit the enter boresight JESTER keybind, half the time he doesnt do it. When he does, and if I select the proper aspect, then it tracks. before that I could CAGE , select proper aspect and it would track almost always. or I could enter BST mode, select the proper aspect, and it would track, from further away. right now, this doest really work anymore for me. the way it works 100% of the time is this: I CAGE... then I ask Jester to enter BST mode. then I select the proper aspect, and then fire and it always tracks. I'll try providing a track of these situations
  12. further testing show that it now works in BRST, but not when I use the cage button as it used to. in using the cage button it ends up locking the target, even though i dont use the nose wheel steering to ask for a lock.
  13. I used to be able to use the cage or boresight and use my radar in flood with nose or foward aspect to hit target head on without a lock pretty easely.. it doesnt work much anymore. did you change anything to it ?
×
×
  • Create New...