What's new

Command line arguments

Raptorstrike

New member
Does Project64 allow any arguments to be passed from the Shell at load-time? I tried passing the name of a valid rom file and it said that it failed to open the file and there is no list of shell commands in the documentation but I thought I would ask anyway

thanks for your help
 

NoeOM

Mankind Member
Ask the developers

squall_leonhart said:
just associate the file types with pj64... theres no point in command lines in pj64
This is not what Raptorstrike want to do. He want to call pj64 with arguments. Associating file types with pj64 will make pj64 open the (rom) file when double cliking on int. Calling pj64 with arguments will make possible to call pj64 and order it to load a rom from an command line, from another program or so.

I think that administrators Jabo, Zilmar or Smiff can answer your question (they closely know pj64).
 
Last edited:

squall_leonhart

The Great Gunblade Wielder
exactly.. dude.
associtate the rom files to pj64, then command line directly to the rom files.
ie, associate .v64 to pj64,

then command line to (exampleddrive):\(example folder)\Legend of Zelda.v64
 

Poobah

New member
squall_leonhart said:
just associate the file types with pj64... theres no point in command lines in pj64
That one made me laugh. What an ignorant thing to say; what's the point of passing file names to a program if it doesn't even process command-line stuff? As I've said to you before, you shouldn't post about things unless you know what you're talking about.

As I have said to you before, try reading people's posts before replying to them:
Raptorstrike said:
I tried passing the name of a valid rom file and it said that it failed to open the file
If passing a valid ROM file name to PJ64 doesn't work, why would associating ?64 file types with PJ64 work? Raptorstrike is right about this, too; I've tested it aswell, and it always says that it "failed to open the file".

Now, about the shell integration problem. There are two bugs in PJ64 regarding this:
-The shell integration adds entries like this:
Code:
C:\N64\Project 64\Project64.exe %1
But they should be like this:
Code:
"C:\N64\Project 64\Project64.exe" "%1"
-Whatever arguments are passed to PJ64, it always says:
error.png
 
Last edited:

Smiff

Emutalk Member
- only cmd line argument pj64 supports is the rom (path\file.ext)
- don't use quotes, pj64 puts them on itself

whether this is a bug is debateable, its certainly non standard (v1.7 accepts both with and without quotes). but it must work because this is how association works and e.g. GameEx frontend loads PJ64 with ROMs perfectly fine.
 

Poobah

New member
Smiff said:
- only cmd line argument pj64 supports is the rom (path\file.ext)
- don't use quotes, pj64 puts them on itself

whether this is a bug is debateable, its certainly non standard (v1.7 accepts both with and without quotes). but it must work because this is how association works and e.g. GameEx frontend loads PJ64 with ROMs perfectly fine.
Oh, I see. That's a bit silly.

Still, PJ64 1.6 still creates entries that don't work, because it doesn't put quotes around PJ64's executable's full path.
 

redmistpete

New member
Does anyone know if there is a command line to switch to a particular GPU plugin when a game launches in v1.6 please? I know people have said that there are no commands for PJ64 but surely there must be a way to change the GPU without having to do it manually with the GUI before launching the game. Thanks, Pete.
 

Top