Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #1 
We have a set of Logitech ATK3 joysticks that we got to use with fighters.  When the fighter deploys they get stuck in a horizontal spin, like the A or D key is held down except it isn't.  All the other functionality works with the joysticks.  I tested them using an online joystick test tool thinking there was something wrong with the joysticks but everything came back normal from the test. 

I have tried multiple joysticks with multiple computers with the same results.  

We have had a logitech X3D for a long time that Helm uses and it doesn't have this problem with the fighters.  

Any ideas of how to fix this?  I assume that no one else is having a similar issue?  

My hunch is that it is going to have something to do with the fact that the X3D has a Yaw function and the ATK3 does not, but I don't know where to start plundering around in the game to try and tinker with that.  


Thanks

__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #2 
Ok so I found the problem. (moments after I posted the above comment) 

In the controls.ini file 

; comment the next line out, if your joystick does NOT twist
FIGHTER_ANALOG_YAW = UI_INPUT_JOY0_AXIS5

My joystick does NOT twist! [frown]


Next question
When I go to edit that file (with notepad) I can't save it after I edit it.  I click save and it tells me the file already exists and I try to overwrite the file and it tells me access denied.  

Thanks for any help

__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
Triphammer

Registered:
Posts: 12
Reply with quote  #3 

1. You need to run Notepad as Administrator.  
Windows 7:  Start > All program > Accessories > RIGHT CLICK on Notepad and choose Run as Administrator

Windows 8:  From the tile view, type Notepad, once it is displayed RIGHT CLICK on it and choose Run as Administrator

Windows 10: click in Search bar and type Notepad.  RIGHT CLICK on Notepad and choose Run as Administrator

2. Once Notepad is running, click File > Open and navigate to the location of the controls.ini file and double-click on it.  You will now be able to modify and save it.

clavestone

Avatar / Picture

Registered:
Posts: 359
Reply with quote  #4 
triphammer is correct. I use an AT3. trigger is beam button 2 is boost, button 3 is break, button 4 is missile, ,button 5 is request dock
__________________
PirateLord Eric Wethington:
Commander of the 1st CAP Light Recon Fleet stationed at ShoShuShen station, Eastern Front Sector
Captain of the Privateer Longbow "Jimi-Saru"
Captain of the Privateer Brigantine "Fulminate" and 59th Pirate Fighter wing "The Reapers"

Charter Member of the Eastern Front online group (PirateLord)



Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #5 
That got it! Thanks Guys.  
__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
ryleyra

Registered:
Posts: 2,999
Reply with quote  #6 
Alternately, you can right click on the file icon in the directory, and select Properties->Security tab and click on the button to Edit Permissions. Then select all checkboxes for All Users. I find it helpful to go in and set write permissions on everything I might edit. (artemis.ini, vesselData, engineering presets etc.)

For some reason, Artemis installs with read only permissions. (Although this might not be the case if you install into a user directory)
Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #7 
Ryleyra I'm really glad you added this bit about the security tab.  I've been working on a DMX setup too and I was about to go crazy running notepad as admin every three minutes to make a change and test!   [smile]

Thanks for all the help everyone!  

__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
ryleyra

Registered:
Posts: 2,999
Reply with quote  #8 
You're very welcome. With me, it was the engineering presets; for the longest time I thought presets had to be set all over again at the beginning of every game. I was thinking a file to hold those presets was a great idea, and then I started seeing an engineering preset file being passed around along with an application that was a preset manager. I thought it was part of that app! [biggrin]

Then I suddenly realized that if I made the Artemis directory read/write, the preset file was written to the folder by Artemis. The feature was already there, but I hadn't installed Artemis correctly.

You know now that I think about it, that's probably something that could be added to the wiki.
Dave Thaler

Registered:
Posts: 502
Reply with quote  #9 
Quote:
Originally Posted by ryleyra
For some reason, Artemis installs with read only permissions. (Although this might not be the case if you install into a user directory)


When you install for "all users", yes it's read-only by default.  When you install "just for me", then it's writable by default.   For example, some missions have mission logs, which only work if you install "just for me" for that reason.   Hence I usually install "just for me".
ryleyra

Registered:
Posts: 2,999
Reply with quote  #10 
Quote:
Originally Posted by Dave Thaler


When you install for "all users", yes it's read-only by default.  When you install "just for me", then it's writable by default.   For example, some missions have mission logs, which only work if you install "just for me" for that reason.   Hence I usually install "just for me".


Thanks. I thought that was the case, but I never confirmed it. I usually just go into the directory and set all applicable files and the Mission directory to writeable.

Since I always apply upgrades to the current Artemis directory (saving a backup so I still have the previous version) once I've set the permissions I don't have to change it again. Also, when I install an Engineering client on someone else's computer, I always copy over my own presets. If they don't want to change it, that's so much the better, since they can't accidently write over it.

Actually, I DID confirm it, and forgot that I did. There's another thread in this forum that goes into the subject in some detail.

Once point I just thought of is that if you install "for all users" and then run as Adminstrator, you can override the permissions protection. So you can use this to write protect your presets; if you want to change them just run Artemis as Adminstrator, if you want them to be restored to their original setting when you exit the game and start over, don't run as Administrator.

Mission logs can be handled the same way. Normally, they are just used for debugging and the typical user doesn't need them.

Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #11 
I didn't know if I should start a new thread for this or not so I'll post the question here first.   

I have recently completed our console build and I am having some issues with joysticks that I hadn't foreseen.  

In the consoles I used a USB joystick emulator to feed the button presses to the computer. Specifically this one:  

http://www.amazon.com/Reyann-Arcade-Encoder-Joystick-Fighting/dp/B00UUROWWK?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o06_s00

I'm using joytokey to emulate the button presses on the console "joy stick" to keyboard keys for Artemis. 

It works great on its own.  The problem happens when I want that station to also play dual roles as a fighter.  For example the engineering station works fine with its console button presses but when you switch to the fighter the games doesn't take any inputs from the actual joystick.  It continues to take commands from the console board.  So you only fly in a straight line which is pretty useless.    

I would like to be able to have both devices simultaneously sending commands to the game so I could toggle between roles.  

I've tried several arrangements in joytokey with both joysticks.  

Any ideas?  I'm pretty under the gun to have this ready for Armada.  

Thanks

__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
techbear

Administrator
Registered:
Posts: 139
Reply with quote  #12 
These are the lines in control.ini, associated w the joystick:


FIGHTER_FIRE               =           UI_INPUT_JOY0_BUTT0
FIGHTER_BOOST              =           UI_INPUT_JOY0_BUTT1
FIGHTER_BRAKE              =           UI_INPUT_JOY0_BUTT2
FIGHTER_LAUNCH             =           UI_INPUT_JOY0_BUTT3
FIGHTER_RECOVER            =           UI_INPUT_JOY0_BUTT4
FIGHTER_ANALOG_ROLL        =           UI_INPUT_JOY0_AXIS0
FIGHTER_ANALOG_PITCH       =           UI_INPUT_JOY0_AXIS1
; un-comment the next line, if your joystick climbs when you want it to dive
;MULTIPLY                   =           -1.0
; comment the next line out, if your joystick does NOT twist
FIGHTER_ANALOG_YAW         =           UI_INPUT_JOY0_AXIS5


Notice that they all use Joystick 0 (zero).  If there was a way to make your USB joystick emulator use joystick 1, they might not conflict.

You could also try changing all the above to joystick 1, and see if that works.

Hyperion Engineer

Avatar / Picture

Registered:
Posts: 91
Reply with quote  #13 
I tried editing them all to JOY1 and that didn't help.  If there is any way to force the joystick board to use a different ID I don't know it.  It would have to be something in Windows because the board is not configurable as far as I know.    

Along those lines I tried commenting out the the keyboard keys for the fighter (just a wild guess) and that let it work for some reason.  It hasn't worked 100% though.  Science, Engineering and Comms are working fine but Weapons isn't for some reason?  I haven't tried Helm yet.  





__________________
Executive Officer and Chief Engineer of the TSN-Hyperion (Concord, NC)

TSN-Hyperion in dry dock at Hephaestus shipyards.
https://artemis.forumchitchat.com/post/tsnhyperion-bridge-build-8068440?pid=1291924499
BzDan

Avatar / Picture

Registered:
Posts: 9
Reply with quote  #14 
Hello,

Changing gears, I need some help with making my joystick work with Artemis 2.4.0 installed on a PC running Win 7 Pro 64bit and 3 monitors on 2 video cards. The joystick is a Logitech Wingman Force 3D, 7 buttons plus hat plus throttle plus twisting.  The stick is kind of old and I cannot find Logitech drivers for it, for Win 7 64bit. However, it uses the operating system's driver, it is identified correctly by the Device Manager -> Human Interface Devices and  I can calibrate it in Win 7's control panel -> Devices and Printers.

I tried it with Artemis 2.4.0 stock, extended and TNG and it does not work with either of them, neither for helm nor for fighter. I looked into Artemis.ini and joystick is initialized. Also, buttons are mapped in the controls.ini.

Any suggestions?
Thanks,
Dan
DagShadow

Registered:
Posts: 14
Reply with quote  #15 
Dan I know this is an obvious question, but the first time I installed my early generation joystick on Windows 7 I had to restart the comp before Artemis could see it, I was still having the same fighter issue at the start of this thread, have you tried restarting the comp? Also have you tried it in another program (sometimes joysticks die in storage)?
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.