Okey Dokey…
Latest posts made by Strafe
-
RE: Weapon Delivery Planner released
Falcas,
Thanks for your reply. Took your advice and created access via network connection. When I start WDP I get the attached error. I go ahead and click continue. WDP opens, and when I try to load any mission.ini (all of which work fine with WDP on the main machine) I’m able to point to the file, but it doesn’t load, No error message, just doesn’t load.
FYI, I wasn’t able to install WDP on the secondary machine with the installer. Saw advice you’d given another guy with the same problem, and just put the application in the program folder. It launches, but maybe that has something to do with the error?
Strafe
-
RE: Weapon Delivery Planner released
Falcas, thanks for developing this software. I’ve only just begun to use it, so I can’t say much about it at this point. I’m running BMS 4.33 U3 and the Balkans Theatre on a one machine and would like to run WDP on a second machine that doesn’t have BMS or Balkans installed (various reasons, space mostly). I have WDP running on the second machine, but can’t open the TE .ini file that I created on the main machine and then copied to the second. I’m guessing that is because WDP wants to access BMS and Balkans data that it can’t find. I don’t want to edit anything on the second machine, just view and reference it as I fly a TE on the main machine. Is there a way to do that without having BMS installed there as well?
-
RE: YAME64 suite
If you are sending over your network I would indeed forward the port.
No joy. I’ll quit bothering you guys about it. I appreciate the help. If I ever figure it out I’ll let you know.
-
RE: YAME64 suite
Should use default 8080 port.
Are you starting the YAME server? And is the item ‘Key server’ checked on at the Server tab in the YAME UI?
Can you check what public IP is mentioned in red on that server tab and verify that is also 3 times the IP you see inside the /htdocs/sender.js?The YAME server is running. The “key server” item is checked.
Does the 8080 port need to be forwarded in my router?
The public address is not mentioned in sender.js, but I’m running on a LAN and the local server address is mentioned three times. -
RE: YAME64 suite
Maybe could be a firewall blocking the calls.
I have my firewall turned off. I’m able to extract gauges to the tablet through 53000. Does the ICP use a different port?
-
RE: YAME64 suite
The server is running on Windows10 64 bit. YAME64 v1.1.0
The tablet I’m using to access the server is Windows10 32 bit. -
RE: YAME64 suite
I am running the ICP in the browser, which is directed to the IP of the server. It has never been clear to me whether or not the client needs to be running in order for the browser ICP to work (given that the ICP doesn’t work, I thought maybe…). I am primarily running the client on the second machine in order to extract other gauges.
-
RE: YAME64 suite
Yes, it is set correctly on the YAME UI globals tab on the machine where BMS and the YAME server reside. Nothing has been set on the Globals tab on the client machine. Does the location of BMS 4.33, the DTC file, and the keyfile need to be set there as well?
-
RE: YAME64 suite
Thanks for your quick response to my question. I’m not sure what you mean by setting my keyfile correctly, but if you’re asking if the BMS (full) keyfile is sending the correct ICP callbacks to BMS, then yes, if I use my keyboard to operate the ICP it responds correctly. Is there some alteration that needs to be made to the keyfile in order for the YAME ICP to work?