Jump to content

vCSG3 Bloat 203

  • Posts

  • Joined

  • Last visited

1 Follower

Personal Information

  • Flight Simulators
  • Location
    vCSG-3 VFA-14
  • Occupation
    VFA-14 OPSO
  • Website

Recent Profile Visitors

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

  1. Thanks again! Checking... 1: I have tried 10308 and I'm positive that 10311 isn't conflicting - since it's a brand new environment and others can easily browse and join my server without punching in the IP. It also appears in the ED browser https://www.digitalcombatsimulator.com/en/personal/server/#allservers 2: Port forwarding looks OK to me: UPnP values: manual forwards: 3 - yes, it's public 4 was the most intriguing, but I don't believe I'm doubleNAT'ed. The router connects directly to my fibre wallbox and its IPv4 is showing the same as shown in wtfismyip when opened from both my gaming rig and the server. and now, for a curve ball candidate number 5... the server runs on a bootcamped Mac Mini box - I wonder if something in the network driver layer is causing the issue - it only just occurred to me that when I've seen it appearing perfectly fine before, with the same router settings, was when the server was running on a native windows machine...
  2. thank you for your advice! Network discovery was indeed off on the server machine (or rather it was set to a public network type instead of a private one), but turning it on (checked pinging by hostname worked) did not bring the server into the browser. I can connect to it over LAN IP (and always could), but no joy on being able to add it to favourites. I wonder if there is a way to edit the favourites list manually somewhere in the config... NB: what does work, is I can now use the machine name to 'connect by ip', just adding the port number afterwards: so that is an improvement
  3. Last night I dropped 4 500lb JDAMs and proceeded to perform gun runs. Every time I used the CCIP gun pipper, it was pointing way too low (several degrees below the VV at all times, even at point blank range). The tracers were visibly moving a good 5-7 degrees further up from the pipper. Manual mode was elevated significantly higher, allowing for some accuracy (but obviously not as good as CCIP would have been). Attached is a track showing this happening - sorry, it is not short: https://drive.google.com/file/d/1dIGklOm31TnXo4DvQBaYeM9sXtyVohI_/view?usp=sharing I tried replicating this with an air started jet for a short track, but there were no JDAMs on the jet, and the behaviour did not occur, so don't have a shorter track to show.
  4. I see what you mean. NB: in the real jet, there is an engineering page you can turn on to see the current trim setting.
  5. Both the FCS page (all trims) and the Checklist (elevator only) page provide effective trim information.
  6. If you want to delve deeper, here's a DCS-centric video presentation we created with one of our IPs, a Raytheon engineer (no classified stuff):
  7. I've searched far and wide, but this specific variation of the issue does not seem to have a listed solution... I am hosting a server, which other people can see and connect to via the in-game server browser. I can also administer the server via the account 'My servers' list and I can connect to it via internal IP no problem. I cannot, however, see it listed in the multiplayer browser, and thus I cannot set it to favourites or make DCS keep the password saved (I can for any other server). I am absolutely certain that this was not always the case - I attributed this to my ISP, but having just changed the service, I'm getting the same thing. Ports are all correctly forwarded (as I said everyone else can see and can connect to the box), but I have to jump through extra hoops to join my own server :S Many thanks for any insight!
  8. Are there any patch notes / change logs available for Winwing firmware releases? Google is difficult...
  9. you're absolutely right
  10. indeed - as do any weapons with variable delivery methods, such as SnakeEyes.
  11. legend, thanks! it's so obvious when you put it like this...
  12. this is intended. the on button needs a long-press on the TCN function. I think it's because TCN is a potential means of revealing jet position in enemy territory.
  13. definitely getting this in the hornet, using 3x TM MFDs and either X52 or the Orion - air spawns always start with a corkscrew
  14. happens to me with X52 and Orion (separately, 1 connected at a time). Hot spawns in the Hornet are fun with the sync function on... bit of a pain to have that option off... wonder if this has anything to do with AI tankers flying with full surface deflections in a straight line... maybe the default positions have been flipped somehow...?
  15. hi again - please find a sample track. All players designated WP 2 as steerpoint 1 and WPDSG WP1 as target area, for each of their SLAM-ERs. Only Bloat's weapons are actually following the route in the track, the rest is recorded on my track as heading straight for the target. One exception - one of Knuckles' missiles was not designated correctly and went super-long - disregard. https://drive.google.com/file/d/1n7nxXEr9tocKAaFz_PMo-_a5e8R3C1H-/view?usp=sharing In reality, all missiles went to their assigned steerpoint and allowed terminal guidance at the correct time, and targets were hit using MITL, at the expected arrival times. sample map view:
  • Create New...