mojoswagger1980

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 76 total)
  • Author
    Posts
  • in reply to: emulated processor goal? #5320

    Got mechwarrior 3 running pretty well at 320X240. Movies and cuts scenes lag video and slightly audio. Also the in game voices are really soft (training instructor and such)and i get this bizarre garbled screech when loading from cd . I assume its fixed with no cd but the load screen and movies are gone so i dont know .

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5319

    hard wiring didnt help . Once again it shows the keys as being mapped but do not map them .

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5318

    Sorry i just saw this post asking for a video . Im going forward with hardwiring it …..just to start with i notice the controller no longer shows up as a dualshock 4 controller on the phone it shows up as a sony wireless controller even though its wired. Ive lost the ability to remap via sixaxis controller and the buttons are no longer correctly keymapped but its detected and id have to say more responsive as far analogs go ive lost use of touchpad but wasnt using it for the game anyway the power button isnt mappable in this state it only attempts bt connection if pushed. Im going to see what happens with magic dosbox now.

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5317

    Ok i got one more idea. I will dig out a usb otg converter.I will hard wire the ps4 controller remap everything and if that works i have no idea what it proves. I know sixaxis controller isnt blocking it because it is the only way to make it accept keymappings currently . I will disregard all of that. I will disregard how lame it is to hardwire a bluetooth controller is particularly this one because it draws power from the phone battery when hardwired. I really dont want to but will because i know it worked the way i have it set. Im not delusional and this may seem petty to you and if so i can only assume youve never tried and succeeded at a controller layout for mechwarrior. Its litteraly took months to evolve to what it is . its not somthing you can just go a different way with or i would have.I guess it comes down to this. If this fails to give me the desired results ill try somthing else entirely.

    P.S. backing up profile saves current controller maps? Or do i duplicate and remap? Nevermind i think i just answered that question twice lol

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5316

    what specifically was the update for? Im wondering if it had anything to do with xboxone controller in the forum . im using a ps4 controller that had no issues til someone complained there triggers dont work on an xboxone controller and your insisting your controller works . im thinking this is just way too coincidental . the Controller keylayout on a ps4 controller is different then that of any other sixaxis controller and your insistence that you just tried an ipega (not familiar with those but im guessing it uses the generic abxy setup ?) makes me wonder if somthing got changed that improved functionality in one device but had the opposite effect on mine . I have tried everything from remapping all controls in both game and app and cannot get the analogs to do except anything otyer than up down left right when mapping as keyboard and also fails when trying to map gamepad keys to analogs. I had my right stick mapped as up (=)
    Down (-)
    Left (,)
    Right (.)
    last night even though these keys are still mapped the only things my analogs do is up down left right. i beleive you when you say they are working on your ipega though im not certain you mapped anything other than up down left right but regardless the point is i beleive you. I would not waste this kind of time on this if i hadnt already had them mapped and know for a fact that my map layout was working prior til i got off work last night. I have ruled out any other potential system app or user app updates. The only thing that changed was this app got an update.Is it possible to get an early version of the app ? It seems like that would be the easiest fix .

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5315

    try mapping somthing nonnn directionnal to them . It simply will not work . And how is duke nukem applicable ? The forward key is forward in that game.

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5310

    Yes, I could map as controller, but the controller is terrible as far as calibration goes . I’ve got it set to none in config. Are you suggesting I map as a controller but just omit the actual stick and just map buttons? If so, I hadn’t considered that, but whenever I map a controller the games want me to calibrate it , how could I do this without the stick? Hmmm I guess I could map as stick, calibrate, then remap as buttons. I can’t help but note that your update requires a lot of concessions on my part. I will not be allowing your app to auto update any longer do to this inconveince.

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5309

    Edit: Ive been playing around with the controls and I’ve discovered that it seems the controls setup wants my triggers to be be gas, brake. I can get other keys to assign to my analogs now except forward and reverse. These always revert back to directional. I do not want to adjust the in game controls setup given how long it took to come up with a feasible control scheme (mechwarrior is control intensive easily over 40 controls, to map this to a PS 4 controller is very difficult it would not work if I had to use the triggers as gas brake, I cannot omit controls and nothing other than gas brake can be mapped to up down and be usable) I’m kind of stuck . is there any way to just go back an update? I don’t know maybe release the old version via this site til a proper fix worked out?

    in reply to: The Update Intended to fix controls Nov.19 has ruined mine #5307

    I use the paid version . the issue I’m experiencing is my analog controls no longer allow any mapping other than directional movement when mapped as keyboard regardless of what I map them too. Both sticks do this . I noticed the issue last night about 6 pm PST. I don’t know how to logcat this issue because magic dosbox allows for remap, accepts remap but fails to remap. Both sticks are stuck with up,down,left,right as map regardless what I set them too .(i.e if I map them to y,z,x,c the app claims it accepts changes but the sticks remain mapped up,down,left,right) I am stuck using the keymapper built into sixaxis controller that works but lacks all the F keys and Ctrl (didn’t realize how often these are used til you lack them) and in order to get sixaxis controller to work it has to be set to input device which negates the keyboard (only 1 keyboard can be active at a time, sixaxis has to take the place of the built in one in order to get the app to recognize it ) Inever had control issues prior and the only thing that’s changed (globally) is an auto-update (yeah kicking myself for not killing that) to your app my phone took at 5pm PST. I checked out the changelog and it said it was an update intended to fix control functionality so I contacted you. I’m sure I’m not your only issue (play store rating went from 4.8 to 4.4, in order to affect that at all would take a considerable number of complaints)for what its worth I didn’t complain via google play I came here.

    in reply to: hdd imgmount question and observation #5296

    Edit: the forth one down is incorrect . it does not result in IMG being mounted as c. You must define fs as something it cannot be none without disk geometry

    in reply to: List of supported Win3.1 and Win9.x Games #5281

    I got the same message on star wars rogue squadron. the d3d patch for mercenaries also screwed the pooch. Try to avoid anything with 3d enhanced in the description with this dosbox build.

    in reply to: List of supported Win3.1 and Win9.x Games #5280

    What did you set vmemsize and processor at? Auto isnt the fastest, pentium is and vmem determines what graphics card the game thinks you have. It is an extremely bad idea to set this above 4 sometimes 4 is too much. This build of dosbox doesnt have munt or a glide wrapper.

    in reply to: List of supported Win3.1 and Win9.x Games #5279

    i thought th3 note 4 was slow til i got it rooted unlocked debloated and off touchwiz(wtf was samsung thinking) now it smashes. Just out of curiosity your note 2 wouldnt happen to be tye sch-i605 would it ? i still have mine and cannot beleive how over clockable it is. It screams but doesnt get anywhere near as hot as its predecessors i also own the note 3(900v) and 4 (910v).you really have to unlock the snapdragons to get any kind of performance but it is there. Its being crippled by samsungs Dvfs. I actually think its working againsts its own hotplug scheme. These phones have gotten hotter with each new model. The 4 would get physically hot to touch when i ran touchwiz…main reason i unlocked was to debloat (nobody anywhere uses half what comes loaded on these and the samsung apps i liked have fell off hard ie side-sync )Running aosp is worlds faster and cooler.

    in reply to: System Cleaner? #5275

    That was litterally worthless. You gave me an example that isnt in anyway applicable.

    in reply to: L2/R2 Not Mappable #5273

    I think the issue is there is no vendor keylayout for the xbox one (i dont see it anywhere in system/usr/keylayout) i wonder if he can trick his device into thinking its an xbox 360 controller? I trick mine into thinking my ps4 controller is a ps3. Does it show up as xbox one s controller when it syncs? Android labeled mine a sony wireless controller which is incorrect in terms of keylayout. I use a third party app (sixaxis controller) to sync it and remapp it might help (requires root)

Viewing 15 posts - 31 through 45 (of 76 total)