Guppy

My Frames in DCS are fine 50-80. It's IKARUS that is having issues. and its the latency of pushing buttons and it responding appropriately. I'll take another video tonight showing you exactly what I mean between ground and air. I run 7 monitors 3440x1440; main, 4x 800x600, 2x 800x1280

I said it in a different thread - these movies are so absurd in all of the best ways. haha love them!

Its so absurd in all of the best ways - I love it haha

Problem: Our HOTAS Throttles have a very limited range of movement compared to the real jet. Even the TMWH Throttle, which arguably has the longest range of motion, loses a significant amount of it's throw. - Ground/Air idle positions in the real bird severely limit the travel movement on our throttles (roughly 20%?) Solution: Get rid of the way ground/air idle positions work in real life and have a more meaningful application to the sim. - Idle should always be at 0% of our throttle vs. 0-20% (or whatever it is) as it currently is. - As we travel forward from 0% we should begin to engage the actual throttles in the sim and thus, RPMs. Purpose/Goal: The purpose is simple, it allows us to have more accuracy in using our throttles, at home, vs. losing a significant amount of throw due to the conflicts of what the real bird is like. - Give us as much range of motion as possible with our HOTAS at home. I appreciate the accuracy in making this as authentic as possible, but just like in the case of the TDC depress/slew; some of the these things conflict with home use vs. what it actually is like.

Let me first say that I really appreciate all of the hard work y'all are doing on the Hornet; a request though. Allow the option for clients to do a full GPS alignment or a quick version that is longer than it is now (instant) and shorter than it is IRL (long). I love detailed, realistic sims. But for me, just sitting and waiting is a bit excessive. I get it; some folks get invigorated watching that timer count, but not me. I'm not asking for quick starts or whatever. - Just make the GPS alignment process faster; 30 seconds? 1 minute? - Allow an option on the server-side/client side to let those folks who want to enjoy the rush of a GPS alignment. I'd also like to see this cascaded to other aircraft like the F14B and A10C. (This is in preparation for you guys releasing the full FPS alignment as stated previously)

HJP: here is what I'm experiencing on a 8700k@5.3, 32GB RAM, 2080TI: ExportScript.Config.ExportInterval = 0.025 ExportScript.Config.ExportLowTickInterval = 0.05

Like others I'm experiencing lag issues between DCS and IKARUS. Even with the following changes there is a significant amount of lag time between gauges in game and IKARUS. My performance in DCS is outstanding... however the lag that has been occuring in IKARUS is odd. I updated to the latest version and still no help (1.5.5.462). I've noticed that when I'm on the ground, powered up there is literally no lag between DCS and IKARUS. However, when I take off there becomes a significant amount of lag in IKARUS updating. This does not seem like it should be occurring - any thoughts? Here my refresh intervals: I've adjusted with like .001, too with no changes.

https://ruffycontrols.com/ Already browsing options! This is amazing!

Fortunately this is false for me. The performance difference between DCS running in Window Mode and IKARUS responsiveness is night and day. I've gained an extra 10 fps every time I set DCS' Affinity level. Additionally, the responsiveness of buttons/switches I have on my UFC are immediate when I change IKARUS' Affinity level. (more on this below) I know other users who have seen similar gains, too. I'm talking about the UI. The messages are sent immediately to the game the moment a button (read: touchscreen) is pushed. However, there is a image on/off process that occurs within IKARUS when a single button has been pushed - the actual UI in Ikarus. Setting the affinity level to the highest, solved the delay. To be clear, I'm not arguing the good reasons. I'm just providing other ways of working around this stuff that has worked for me, while we perpetually wait for an update. I Do not disagree with the need/want...but having stumbled on this and experiencing these issues myself, it seemed like a great time to offer some workarounds, too. The suggestions are upgrading your PC and setting Affinity level. Admittedly though, your mileage may vary. I am aware and my assumption is that VR is prioritized in front of simpit builders, unfortunately.

It's got to be located somewhere though, right? If you needed to update it where would you go? Or is it super secret? lol

Hey There again - Question, If I wanted to change the look of the stock F-18c guages (IE: Radar Altimeter, Compass, Etc.) Where would I go to change those files? In the Textures3D file I dont see where any of those are located. Somewhere I've got to imagine there are image files that I can edit/overwrite but I cannot located them. Thanks!

Version 2 of my SimPit is about to be reality. See more here! https://guppy.home.blog/2019/04/11/getting-closer-to-fabrication/

I guess with my beastly system it's not an issue. 2080ti, 32gb ram, 8700@5.3ghz all liquid cooled. But I could see not as strong PCs encountering issues regardless of priority. Currently, this has made it perfect for me 50-60fps even on the most demanding of MP servers.

Multiplayer. Most servers dont allow HUD only views.

There is a workaround I have figured out to this that makes timing almost seamless on the same PC: 1) Open Task Manager 2) Go to Details Tab 3) Right click DCS.exe (after its already launched) and set Priority (processing priority) to Realtime 4) Do the same for IKARUS (Note: you'll have to do this every time you launch the game/IKARUS) This will give both those applications the highest priority. This should help you. I run a very elaborate setup (check my signature) and my response time between exported instruments, touchscreen UFC and such have nearly no delay. FPS is also significantly better in DCS even in window mode for those MFDs.

IKARUS has this same functionality. You essentially create two images (on/off) when one Off is the static image and on is the interaction. Look in my signature to see my blog; you'll see a custom UFC I've created using a similar technique. The nice thing about the touch interface is it can be customized for any aircraft (A10, F14, M2, etc.)

Thank you! I'm working on a new version now. Couldn't do it without your IKARUS software - so thank you!

SA Page you can only interrogate friendlies because you need multiple sensors to confirm hostile. Likely, if you cannot ID them as friendly on the SA page (show as neutral) then they are going to be enemy since in DCS we don't have random planes flying around. But to confirm hostile, you must use the radar.

Actually, I fixed this issue. I set the priority in windows task manager as the highest. No issues now. You might want to add this to your FAQ or install guide.

I'm not sure if the issue here is with IKARUS itself or the DCS Export Script. Here is what I'm encountering in the FA18: - When on the ground in the hornet the buttons/switches respond very swiftly. - When I take off things start to lag ever so slightly. Basically when I use IKARUS buttons they lag in the air, but on the ground they do not. What I mean by lag is I push a button on the touch screen and IKARUS is ever so slightly to respond. 8700k; 32gb RAM; 2080TI IKARUS Version 1.5.5.455 This is my export Config:

LTWS is basically a "soft lock". You hover over the contact on the radar and it gives you speed, alt and direction. The bandit does not know you are "soft" locking them.

I can confirm that the current BETA patch fixes this issue. Thank you very much ED!

Looks like there was an update for this issue in Open Beta - I'll check later this afternoon to see if I notice any performance impacts of the SA page.

In windows I believe you just need to set your middle screen as your main monitor (the one that will populate a taskbar. DCS by default populates whatever is set as your main monitor.

No that's referring to the TDC cursor that it should populate on top of any other image on the SA page. There were symbols that would populate over it, making it hard to read which is not correct behavior.