Maulkin Posted December 1, 2017 Share Posted December 1, 2017 The police light is still not working in 1.5.8.12162 as far as I can tell. --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
QuiGon Posted December 24, 2017 Share Posted December 24, 2017 (edited) This bug (messed up INS display, see screenshot) keeps haunting me since the Mirage has been released, but I still haven't figured out what really causes it. I have decided though, to finally make a report on this one as it the bug just occured again on my last flight a couple of minutes ago. I'm attaching a track file of this flight, where bug occurs around the time my fuel state reaches ~1000kg (don't know the time, sorry). It happend when I wanted to input coordinates for WP3. Coordination input worked fine for waypoint 1 and 2 before, but it bugged out on waypoint 3. Edit: Can't upload track file as it is too big... Edited December 24, 2017 by QuiGon Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
myHelljumper Posted December 24, 2017 Share Posted December 24, 2017 Yep saw that bug. You can fix it by inputing anything in one of the windows, it will clear the screen. Helljumper - M2000C Guru Helljumper's Youtube https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA Link to comment Share on other sites More sharing options...
Gliptal Posted December 24, 2017 Share Posted December 24, 2017 Have reported this multiple times already, I guess we'll have to wait for the systems guy to finish his work on the Harrier. Link to comment Share on other sites More sharing options...
QuiGon Posted December 28, 2017 Share Posted December 28, 2017 (edited) Yep saw that bug. You can fix it by inputing anything in one of the windows, it will clear the screen. I tried that and it didn't work. It just made it worse as digits appeared on top of other digits. Edited December 28, 2017 by QuiGon Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
mvsgas Posted December 28, 2017 Share Posted December 28, 2017 Does it happen in single player or only in multiplayer? To whom it may concern, I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that. Thank you for you patience. Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true.. Link to comment Share on other sites More sharing options...
QuiGon Posted December 28, 2017 Share Posted December 28, 2017 Does it happen in single player or only in multiplayer? I haven't flown the Mirage in SP, so I can't tell. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
Sceptre Posted February 4, 2018 Share Posted February 4, 2018 Let's say I have 7 waypoints in my flightplan. I am going to create a new one, so I select waypoint 08 as my PREP, bu then sometimes my INS will display a 'corrupt' screen (all the numbers overlapping in each section) and I will be unable to create any new waypoints from that point on. The corrupt numbers go away when I exit waypoint 08 as my PREP and punch in any number under 08, but they will return when I try again. Sometimes I get a game crash shortly after; I will attach a log file. It's late here now, but tomorrow I will try to replicate this and post screenshots. If I am doing something wrong in the INS management and it's simply pilot error and not a bug, please let me know, thanks! RTX 2070 8GB | 32GB DDR4 2666 RAM | AMD Ryzen 5 3600 4.2Ghz | Asrock X570 | CH Fighterstick/Pro Throttle | TM MFDs | TrackIR 5 Link to comment Share on other sites More sharing options...
myHelljumper Posted February 4, 2018 Share Posted February 4, 2018 No, it's a bug. I think I already reported it but I never got a crash after it happened. Thank for the report and the logs anyway ;). Helljumper - M2000C Guru Helljumper's Youtube https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA Link to comment Share on other sites More sharing options...
Frederf Posted February 5, 2018 Share Posted February 5, 2018 I've had this "garbage data" issue with the next waypoint but I simply closed my eyes and started entering the new Lat/Long and everything worked out. When I entered the north data the east data initialized to all zeroes. I think it didn't update the display until I pressed INS at the end of the string which makes it harder to enter a valid sequence blind. It's some kind of issue with undefined data being called up which expects well-behaved data. The call needs error checking or something on invalid return. Once that data slot is given well-behaved data everything seems to run normally. 1 Link to comment Share on other sites More sharing options...
Sceptre Posted February 5, 2018 Share Posted February 5, 2018 I've had this "garbage data" issue with the next waypoint but I simply closed my eyes and started entering the new Lat/Long and everything worked out. When I entered the north data the east data initialized to all zeroes. I think it didn't update the display until I pressed INS at the end of the string which makes it harder to enter a valid sequence blind. It's some kind of issue with undefined data being called up which expects well-behaved data. The call needs error checking or something on invalid return. Once that data slot is given well-behaved data everything seems to run normally. ah okay good to know, thanks. next time it happens I'll try and input the waypoint anyway RTX 2070 8GB | 32GB DDR4 2666 RAM | AMD Ryzen 5 3600 4.2Ghz | Asrock X570 | CH Fighterstick/Pro Throttle | TM MFDs | TrackIR 5 Link to comment Share on other sites More sharing options...
lemoen Posted February 9, 2018 Share Posted February 9, 2018 Can I bump this one up? I tried the INS Bombing training today and Mk82 (haven't tried others) don't release on cue, they release as soon as the trigger is pulled. Link to comment Share on other sites More sharing options...
escaner Posted February 9, 2018 Share Posted February 9, 2018 Same here. BTW, the "wings" guidance cues for CCRP aren't supposed to be roll commands that guide you to the release point as a flight director? They actually are implemented as bearing deviation, which is weird for such interface. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
PB0_CEF Posted February 16, 2018 Share Posted February 16, 2018 Now that the precise procedure is detailled in the brand new manual it should be fixed or explained in this manual because new pilots will not understand why bombs are launched as soon as they push the trigger :book: [/url]All known Dynamic Campaign Engine Campaigns Last DCE news : Crisis in PG - Blue version Link to comment Share on other sites More sharing options...
Esac_mirmidon Posted February 16, 2018 Share Posted February 16, 2018 Wait for systems updates. This is known and scheduled for beeing fixed " You must think in russian.." [sIGPIC][/sIGPIC] Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´ Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4 Link to comment Share on other sites More sharing options...
baltic_dragon Posted February 17, 2018 Share Posted February 17, 2018 Now that the precise procedure is detailled in the brand new manual it should be fixed or explained in this manual because new pilots will not understand why bombs are launched as soon as they push the trigger :book: Good idea, I will add it to my list. Link to comment Share on other sites More sharing options...
D4n Posted February 17, 2018 Share Posted February 17, 2018 Are you guys aware of this bug, already fixed in internal build? DCS Wishlist: 2K11 Krug SA-4 Ganef SAM, VR-TrackIR icons next to player names in score-chart PvP: 100+ manual player-kills with Stingers on a well known dynamic campaign server - 100+ VTOL FARP landings & 125+ hours AV-8B, F-14 crew, royal dutch airforce F-16C - PvP campaigns since 2013 DCS server-admins: please adhere to a common sense gaming industry policy as most server admins throughout the industry do. (After all there's enough hostility on the internet already which really doesn't help anyone. Thanks.) Dell Visor VR headset, Ryzen 5 5600 (6C/12T), RTX 2060 - basic DCS-community rule-of-thumb: Don't believe bad things that a PvP pilot claims about another PvP pilot without having analyzed the existing evidence Link to comment Share on other sites More sharing options...
microvax Posted February 17, 2018 Share Posted February 17, 2018 A2G designations work as expected, but the magic slave is broken in the last update. You have to point the missile at the target in boresight, lockon is impossilbe via radar designation. [sIGPIC][/sIGPIC] *unexpected flight behaviour* Oh shiii*** ! What ? Why ? What is happening ? Link to comment Share on other sites More sharing options...
birkenmoped Posted February 17, 2018 Share Posted February 17, 2018 (edited) Hi DanielNL How's about a screenshot? It would help to understand what problem you have and if others can confirm this "bug" !? Birkenmoped Edited February 18, 2018 by birkenmoped Link to comment Share on other sites More sharing options...
D4n Posted February 18, 2018 Share Posted February 18, 2018 When locking in narrow mode, then unlocking this happens... DCS Wishlist: 2K11 Krug SA-4 Ganef SAM, VR-TrackIR icons next to player names in score-chart PvP: 100+ manual player-kills with Stingers on a well known dynamic campaign server - 100+ VTOL FARP landings & 125+ hours AV-8B, F-14 crew, royal dutch airforce F-16C - PvP campaigns since 2013 DCS server-admins: please adhere to a common sense gaming industry policy as most server admins throughout the industry do. (After all there's enough hostility on the internet already which really doesn't help anyone. Thanks.) Dell Visor VR headset, Ryzen 5 5600 (6C/12T), RTX 2060 - basic DCS-community rule-of-thumb: Don't believe bad things that a PvP pilot claims about another PvP pilot without having analyzed the existing evidence Link to comment Share on other sites More sharing options...
Dagger71 Posted February 18, 2018 Share Posted February 18, 2018 Looks like you are using Bscope set to 15 degrees balayage in TWS set to a range of 40nm, with your antenna offset to the left. What is the issue? Now when you unlock it should not revert to 40nm TWS. It should only be set to range in use in close AA special mode. Link to comment Share on other sites More sharing options...
microvax Posted February 19, 2018 Share Posted February 19, 2018 There is some weird behaviour to this bug, it doesnt allways kick in, I will check if I can find reproducable conditions. [sIGPIC][/sIGPIC] *unexpected flight behaviour* Oh shiii*** ! What ? Why ? What is happening ? Link to comment Share on other sites More sharing options...
Knock-Knock Posted February 19, 2018 Share Posted February 19, 2018 Aha! So it wasnt just me fumbling. Yea I have had this happen too, and just had it down to me, forgetting how to operate the darn thing :) - Jack of many DCS modules, master of none. - Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS. | Windows 11 | i5-12400 | 64Gb DDR4 | RTX 3080 | 2x M.2 | 27" 1440p | Rift CV1 | Thrustmaster Warthog HOTAS | MFG Crosswind pedals | Link to comment Share on other sites More sharing options...
Martini Posted February 21, 2018 Share Posted February 21, 2018 I've had this issue as well. Sometimes it works, sometimes it doesn't. I've also had instances where putting the cross on the target's tailpipe at 1-2nm doesn't give me a tone after it failed to slave so I am wondering if it's a problem with the missile or seeker not actually being selected/activated. I will try to reproduce it in isolation and see how to fix it (toggling master arm and pca selection off and on would be my first guess as how to get it working again). Link to comment Share on other sites More sharing options...
Ala12Rv-watermanpc Posted February 21, 2018 Share Posted February 21, 2018 What I have figured out so far is: -In single player: it works fine always -In multiplayer: It NEVER works can anyone test this? bye! Take a look at my MODS here Link to comment Share on other sites More sharing options...
Recommended Posts