The Stupid Questions Thread.

Pfhorums news can be found here. Have a question or suggestion for the Pfhorums? Ask it here.

Re: The Stupid Questions Thread.

Post Aug 3rd '16, 03:09

No, see, in order to make the community helpful and more friendly, we have to start answering people's questions, whether we know the answers or not.
User avatar

Wrkncacnter

Post Aug 3rd '16, 03:48

3371-Alpha wrote:Just because something's commonly used in a particular way doesn't make it conventional.

https://www.google.com/search?q=define+conventional wrote: based on or in accordance with what is generally done or believed
User avatar

Pfhorrest
California

Post Aug 3rd '16, 14:59

JonathanM2D wrote:Hello. I just discovered the website. And it seems really good. I got a Question. I'm playing on Marathon 2: Durandal with AlephOne and I can't get the exact same controls than on the XBLA release with an Xbox 360 gamepad.
When I try to map the left and right triggers, the D-Pad and the right joystick, the game don't want to recognize them.R
And it's pretty annoying because I don't want to use LT and RT to look left and right anymore. Is it possible to map these buttons without needing Xpadder or other 3rd party softwares ?

I know this is a bad excuse, but sorry if I made errors in the text I am french.


As I think you've realized, Jonathan, I don't think anyone has solution to your problem. I feel like there should be some relatively simple way to remapping LT and RT, so I hope you figure something out.
User avatar

philtron

Post Aug 3rd '16, 15:50

philtron wrote:
JonathanM2D wrote:Hello. I just discovered the website. And it seems really good. I got a Question. I'm playing on Marathon 2: Durandal with AlephOne and I can't get the exact same controls than on the XBLA release with an Xbox 360 gamepad.
When I try to map the left and right triggers, the D-Pad and the right joystick, the game don't want to recognize them.R
And it's pretty annoying because I don't want to use LT and RT to look left and right anymore. Is it possible to map these buttons without needing Xpadder or other 3rd party softwares ?

I know this is a bad excuse, but sorry if I made errors in the text I am french.


As I think you've realized, Jonathan, I don't think anyone has solution to your problem. I feel like there should be some relatively simple way to remapping LT and RT, so I hope you figure something out.[/quote

I think that Aleph One doesn't recognize LT and RT and the right joystick as buttons. So I think that's why I can't re-map them.
JonathanM2D

Post Aug 3rd '16, 18:11

Well it sounds like you're able to use LT/RT to look left and right? If that is true then I think that means that Aleph One DOES recognize those buttons; otherwise, how could you use them to look left and right?
User avatar

philtron

Post Aug 4th '16, 21:33

Wrkncacnter wrote:No, see, in order to make the community helpful and more friendly, we have to start answering people's questions, whether we know the answers or not.

RyokoTK wrote:whyd you fuckin' spout off about controllers then, moron

As you can see we treat each other with a great deal of respect in this community (my ass).
PowerMac G5 Dual 2.0GHz 2003 (Model: 7,2)
Mac OS X 10.5.8 (Leopard)
7GB RAM (OWC PC-3200U-30330 DDR SDRAM 400MHz)
ATi Radeon X800 XT (GPU overclocked to 500MHz, VRAM to 550MHz)
User avatar

3371-Alpha
Veldin Orbit

Post Aug 4th '16, 21:59

3371-Alpha wrote:Thank you Wrk for uselessly repeating a point I already tried to make


3371-Alpha wrote:Wrks a dick


3371-Alpha wrote:For a while I was worried that the only thing this community cared about was useless netmaps & other crap, but you renewed my faith.


3371-Alpha wrote:As you can see we treat each other with a great deal of respect in this community (my ass).


Agreed. You're such a nice person yourself. I don't know why you're being a dick to Windbreaker, of all people.
User avatar

Wrkncacnter

Post Aug 5th '16, 02:39

patrick wrote:one of "us"

You said it, not me. Though to be fair most of mine were called for.
PowerMac G5 Dual 2.0GHz 2003 (Model: 7,2)
Mac OS X 10.5.8 (Leopard)
7GB RAM (OWC PC-3200U-30330 DDR SDRAM 400MHz)
ATi Radeon X800 XT (GPU overclocked to 500MHz, VRAM to 550MHz)
User avatar

3371-Alpha
Veldin Orbit

Post Aug 9th '16, 18:41

Unrelated: did anyone happen to save Phobos-Romulus's old pic of the Marathon AIs (the one where they're all floating heads a la our brief glimpse of Durandal's avatar in M1)? I asked him about it a while ago and even he couldn't find it again.
welcome to the scene of the crash
User avatar

General-RADIX

Post Nov 21st '16, 15:59

Also, how can you edit the FOV for Rubicon? Copypasting the FOV script into the Scripts folder doesn't work unlike with all the other scenarios, and I don't want to go back to playing with headaches.
Tunaspirit

Post Nov 21st '16, 20:01

If it's anything like Eternal, there's probably a FOV tag either in a script that's taking priority over the FOV script you want to use, or else embedded in the map file (and thus taking priority over all external scripts). You'll have to find where that FOV tag is and remove it for your FOV script to work.
User avatar

Pfhorrest
California

Post Nov 21st '16, 20:59

Pfhorrest wrote:If it's anything like Eternal, there's probably a FOV tag either in a script that's taking priority over the FOV script you want to use, or else embedded in the map file (and thus taking priority over all external scripts). You'll have to find where that FOV tag is and remove it for your FOV script to work.

Thanks for the help, I opened the Rubicon Map.sceA file in Rubicon Data with Notepad++ and replaced all the instances of all the <view> blocks including the <fov> tags with a blank space, and the FOV script worked fine after that.

EDIT: Ok, while I managed to get a higher FOV, doing so borked the fog, as many other textures and terminal picts were missing. I tried to only edit the fov normal values to 120 rather than deleting all FOV blocks entirely, but the same problem still persisted. After some further testing, I discovered that through replacing all the <fov normal="XX" entries (both =80 and =90, excluding the comments) the only maximum allowable FOV for Rubicon is 99 before it starts glitching out, as any FOV values including 100 or higher cause the fog and terminal picts to not display. 99 is an improvement over 80, but I still want to reach 120. I have no idea what causes Rubicon to glitch out with a FOV higher than 99, maybe it's the rate=x in the FOV tags, but I'm not entirely sure. Does anyone else know what's the deal?
Tunaspirit

Previous

Return to The Pfhorums



Who is online

Users browsing this forum: No registered users

cron