Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Killbotvii

Pages: [1]
1
The save was incorrectly uploaded here: https://openxcom.org/forum/index.php/topic,6596.msg157672.html#msg157672
I don't think I've ever managed to do that before, whoops. I had that thread up ensure there wasn't some oddity I should mention before posting, didn't realize I was posting in it!

2
OXCE Builds & Ports / Re: OXCE v7.9.8 MacOS
« on: September 13, 2023, 07:07:19 am »
Here you are! Running a few submods but they're all cosmetic apart from the one that makes me begin in 1994. Not sure if that messes anything up without it. Likely doesn't, but including it anyway. Hope it can be resolved!

If it helps, I"m using the M2 Macbook Aiir, specifically the ARM build of OXCE.


Meant to post this on a totally different board, in a totally different thread. Whoops.

3
I'm having a problem where, even if I'm using this as the sole submod, there are huge problems with graphics. The most egregious I've found so far is the inventory display for the riot armor, which results in most of the screen being white. In-mission, the armor displays correctly, but then I briefly caught a glimpse of an enemy that became a white square later on, though I wasn't able to capture that because I couldn't find them again.

I am using XCF 3.1 and OXCE 7.9.10.

4
OXCE Builds & Ports / Re: OXCE v7.7 MacOS
« on: August 26, 2022, 04:45:14 pm »
I cannot reproduce the success of the ARM release from earlier this year. When I compile it on my M2 MacBook Air, following the instructions he said to follow, it compiles fully but instantly crashes when you try to launch it.

In addition, the working build runs unbearably slow, worsening the higher resolution you run it at. Even at sub 1080p, it's near unplayable and definitely not enjoyable.

5
Android version was never tested on Chromebook.

If you find any Android bugs, you can report them to @sfalexrog on github: https://github.com/sfalexrog

If you find any Chromebook bugs, you'll probably need to fix them yourself.
Understood. I did ask in the Discord the best place to report these and this was where I was told to put it, so I apologize if this wasn't where it should have been put.

6
Over the past week or so I've been playing The X-COM Files on my android phone hooked up to mouse and keyboard as well as my chromebook. I've compiled a list of issues that I've collectively run into.
  • Auto edge scrolling with mouse sometimes stops working entirely. Triggered still works. Chromebook-exclusive problem.
  • Random black flickering across parts of the screen. Possibly related to ChromeOS and has not occurred on my phone as of yet.
  • Escape stops working sometimes. Workaround: you have to switch to a different app and then return.
  • Control-clicking items in and out of an inventory sometimes stops working. See above for workaround.
  • Disabling "List-drag scrolling" does nothing, it remains on regardless.
  • Sometimes lists will think they're being dragged when the mouse is simply hovering over them. Workaround: close and reopen the application.
  • Sometimes cycling through inventories briefly puts the mouse right over the "belt" section and then jumps it back to its previous position. randomly fixes itself.
  • Sometimes when tabbing back into a battlescape scene, the UI for the inventory reverts to original scale(as opposed to filling the screen) and the battlescape UI disappears entirely. Workaround: Save and reload.
  • Small black box frequently appears above and to the left of the cursor and stays attached to it. Disappears randomly.
  • mousing over the ^ and v buttons for adjusting quantities in lists will sometimes trigger the action for the mouse wheel being used, meaning any time the mouse is over it, the values rapidly change upwards or downwards.
  • The "show cursor" option does nothing.
  • The mouse is always invisible when you start the application. Workaround: Manually change the mouse mode back to extended, even if it's already selected.
  • The cursor stopped appearing on the chromebook as of May 24th at 10:25 PM EDT. I believe there is some sort of regression going on, as the edge scrolling and the jumping cursor issue both cropped up at the same time hours prior. Workaround: Shit you not, "show cursor" works now.



Pages: [1]