Jump to content

dorianR666

Members
  • Posts

    1625
  • Joined

  • Last visited

Everything posted by dorianR666

  1. i confirm this i confirm this too nice catch, it sounds like a probable cause.
  2. but did you disable the game mode? settings are saved in user directory, not installation directory.
  3. thanks for quick reply, BN
  4. thank you, very informative. im too used to just clicking an alignment button of gyromagnetic compasses...
  5. YEP THATS IT @BIGNEWY is this known? the lightbulb can die but the replacement mechanics isnt implemented, despite what the manual says. it appears that ground repair can fix it, but the lightbulb dies rather often - at least so far for me, sometimes within minutes of flight as in the last track.
  6. another one sight_fail.trk the sight disappears at 08:02:00, track ends shortly after the manual mentions that gunsight lightbulb can die and describes a procedure on page 169 how to replace the lightbulb, but its not implemented. perhaps the dying is implemented but the replacement was forgotten?
  7. ye so the purely magnetic compass is more of a... back up?
  8. it appears the best view possible is to move camera max forward, max left. stick will only be in way if forward or left of center. i tried editing snapview lua file manually but it seems same exact restrictions apply as when moving camera with keyboard in game, so no fancy top down view behind/above stick that i'd like.
  9. i see well that certainly is sus
  10. hello, very new spitfire pilot here how can i access the compass when in flight? no matter how i position the camera, the stick is in the way and i dont see the compass. i cant find any "hide stick" control, there is no clickable area on the stick either to make it disappear (like in hornet for example). hide stick checkbox in game settings is ignored. of course i can move the stick out of the way but that can be done only on ground, not in flight for obvious reasons. how can i get clear view at the compass?
  11. the 8nm constant is for daytime and 5:15 is considered nighttime i believe. contrast itself has no impact sadly.
  12. Install Audacity. Its free software capable of recording into OGG. WAV is absolutely unacceptable, the files are huge because there is no compression. WMA has poor compatibility in software world because there is no publicly available full specification, using it means either Microsoft's codec or reverse-engineered opensource attempts. OGG, which is what DCS uses, is superior.
  13. its the wrong button weapon release button is used for AG weapons, trigger is used for AA weapons.
  14. no, its just the bricks working correctly now and having a trail
  15. looks like the same thing i reported recently as far as i know, i wasnt giving any attack commands, but i could be mistaken.
  16. yeah i run repair after every bigger update, for that reason, and delete the shader folders. my apologies if my previous post sounded rude, that wasnt my intention. thats another valuable piece of the puzzle. so far everyone affected was using a GPU with GCN 4 architecture, but Vega 64 is GCN 5.
  17. Most interesting post, thanks. Unfortunate about the bay if true.
  18. hi i am not amd drivers version 21.3.1, should be the latest i have also tried setting all those driver options to either "use application's settings" or disabled. it made no difference.
  19. LMAO i literally only asked a question why it cant carry bombs in the bay, devoid of any emotions, because i genuinely didnt know and the post i replied to said "loads of" (which i assume means more than 2, im not native english speaker tho). amazing "adult", to use your expression, response. if you cant reply without personal invectives (appears to be a common theme after clicking your profile), then simply dont reply to me in the future. i would truly appreaciate it, thank you DD_Fenrir.
  20. i confirm this bug, automatic lasing cuts too soon.
  21. of course it is unlikely the game would damage itself in the same exact way for all 3 of us with the same GPU family...
  22. yes beside being off detailed part of the terrain as Bunny Clark says, there is a bug that sometimes makes a part or all of hornet's map be replaced with black. usually the map returns back after about 10 seconds for me. rarely, it flickers on and off for a second. i dont know what triggers it but it happens uncommonly and fixes itself after some time.
  23. some new info when im parked in hornet in novorossiysk, it happens. when i take off from hornet in novorossiysk, it stops happening. when im parked in hornet in batusmi, it doesnt happen. when im parked in l-39 in novorossiysk, it doesnt happen. when im flying any aircraft at any place, it sporadically very rarely happens for a fraction of second. when im parked in hornet in novorossiysk and i switch to free camera but dont move (= it stays in cockpit head position), it happens. as soon as i move the camera, it stops happening (same way as when i take off). conclusion: the bug occurs when camera is at particular Y coordinate or coordinates.
  24. i can make it carry only 2 bombs at most. thats not much, spitfire can carry more. why cant the bay carry anything?
  25. youre right, the trigger action is gone
×
×
  • Create New...