Jump to content

Jabbers_

Members
  • Posts

    967
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Jabbers_

  1. Just a little teaser for now, more content to come, but it will probably be a bit as there is a lot to cover/learn/absorb
  2. Ya ED changed the skin background I need to investigate a fix
  3. For the hotkey I think the default is numpad period, not regular period
  4. :music_whistling: I can neither confirm nor deny
  5. Need to look at your twitch2dcs.log file (be aware your oauth key might be logged in it, so dont post it directly here). You can PM me, hit me up on discord as well, take the oauth key out of the file before sending, or something, i need to remove that from the logging in the future for this reason. Additionally did you reboot DCS after you entered the code? As for it not hiding, not sure, i'd have to try, i know ED made some changes to the MP chat window (which this is based on) in 2.5.4 so need to investigate when i get time, perhaps something broke.
  6. Someone delete this thread, not gonna post it here since 1/20 clips has IL2 and ED is gonna delete it anyway. 99% DCS cant have that unfortunately.
  7. It hooks directly into the twitch api only
  8. I support it still, but forgot to flag this thread to notify me of comments so lost track of it till now. I still use it to this day, infact just reinstalled it with no issue to my surprise :) Not a fan of this method, its intrusive, pain to setup for every stream I do. Ya I had lots of problems with it in the past, even if its fixed now, its still really intrusive.
  9. They originally detailed that you wouldnt be able to use the buttons on the HOTAS, just movement of the stick and throttle so I doubt slew will work.
  10. As stated by ED in the past, they dont typically use SDKs like that as it would give an advantage to a hardware manufacture and they didn't want to do that.
  11. Nope screenshots are just dumping the frame from the left eye to disk.
  12. Figured the community might be missing something like this, I’ll be adding these to the SplashOne gaming YouTube account and not mine as to not try and gain views on my personal account from others. The SplashOne account has been setup to not monetize, but that doesn’t change copyrights found in the songs of the clips in the videos. If you have any feedback let me know, hopefully you enjoy these and maybe it will inspire more streamers to clip more content :) 7LmcVlbLgPg sZAslF1PUfw
  13. Having tried both, the SDE is much smaller than the Vive Pro. Thus perceived better image quality
  14. You are right, zip lip not zip line, my bad, thanks for the correction.
  15. is it just looking at time from DCS or is it looking at CPU time from just your PC? I've never used it. Also was all of this during loading of a mission, or actual gameplay, or both? So many variables. The best way to test would be to replay a track and only bench during the track replay.
  16. Yes, 1 core 100% or 4 cores ~25% (on dcs only) 100% on all cores could be other apps, i doubt it was 100% all just dcs. If you are using the windows CPU performance page to gather these stats it can be deceiving, but without showing exactly what you are talking about its hard to say. If your GPU is hitting 100% chances are you are GPU bound, but you also want this over CPU typically. Most games are GPU bound. In VR its even easier to be GPU bound if you up your pixel density.
  17. Sorry DCS uses 2 threads, one for sound, one for everything else... so there will be a bit more CPU % here as well, so 5% for sound then... Windows will try to spread the workload as much as it can on a single threaded application, so it will try and make your machine not use just 1 core for a single threaded app, adversly a multithreaded app could potentially use 1 thread per cpu and peak each cpu core at 100%. Hope this helps explain that, if not I can try again ;)
  18. I should really just make a video about this haha
  19. My awful paint skillz (its 5nm diameter not radius) Does that help? Here is the carrier quals version (official)
  20. So, unless in training, typically what happens is, From what I remember from my research when making my CASE I recovery video and all the talks with navy pilots I had... and without finding my notes is this. Call in to marshal outside the 10nm bubble Marshal gives you BRC, and stack # to hold (holding altitude can be calculated from your stack #, so stack 2 would be angles 3000, since the base is 2000 where stack 1 would be) You get to your max E speed (250 KIAS) and at your assigned altitude before entering the bubble Once there you enter the bubble and proceed to enter marshal stack, once in the stack you visually watch the ships below you If the person at stack 1 pushes for charlie, you descend between position 3 and 1 of the holding pattern (positions are 1,2,3,4 starting at the boat and moving counter clockwise every 90 degrees, you descend 3->1 and ascend if necessary 1->3) Proceed to approach from stack 1 at proper time. Typically you should have a rough idea how how long it takes for you to get to the approach pattern, and perform it, so given charlie time of 35, and lets say it takes you 5 minutes to get on deck from marshal 1, you can assume to push at 30. But you are also watching to make sure you are de-conflicted with everyone else. This whole process is called zip-line, its as COMMS free as possible, only use COMMS when a problem comes up . Typically there are no COMMS from the LSO as well, unless you request them (having issues) or the LSO spots trouble and is trying to help you not smash into something, someone, foul deck... etc. LSO typically says nothing outside of training, or shitty weather visibility situations. The assumption is, you know what you are doing and unless they spot something unsafe they will not talk to you. Now, that said, if you bolter, the next time around they might give you a couple words to just kind of, reassure you as you approach, and with each consecutive bolter they might increase the amount of help jsut because you obviously are having issues. (anyone more qualified feel free to correct anything I've said... again, all from memory from interviews and discussions from pilots)
  21. DCS is single threaded, windows tries to spread the workload across all the cores (so long as your affinity is set to do so). So if you take the number of cores and multiply DCS CPU% you will have a much more true number... example, 4 cores 25% = 100% cpu, and there for CPU bound not GPU bound. DCS is generally CPU bound on high end system people use for VR (your 1080/Ti builds)
  22. The groove is when you go wings level (on final) after the approach turn. I suggest:
  23. Nope, its called a Zipline, CASE I, everyone gets their position in the stack from marshall, and from that point on says nothing, just eyes out, and unless someones charlie time needs to be changed, arrive on deck at charlie, no comms required.
  24. If you are doing it proper (zipline) you don't use comms :)
×
×
  • Create New...