Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Fictitious Rotor

Members
  • Content count

    12
  • Joined

  • Last visited

  • Days Won

    1

Fictitious Rotor last won the day on March 24

Fictitious Rotor had the most liked content!

About Fictitious Rotor

  • Rank
    Junior Member

Contact Methods

  • Minecraft
    Fictitious_Rotor
  • GitHub
    Fictitious-Rotor
  1. Fictitious Rotor

    Edit LUA_PATH

    Is there a file I can change somewhere, either on a computer in the mod or in my minecraft files so that I can modify the LUA_PATH variable? I'd like to add another directory to it!
  2. Fictitious Rotor

    Multi program server for base

    What you're looking for are daemons/services. These are programs that run in the background while your gui is available in the foreground for you to use as normal. Trouble is, they're kinda complex it took me far too long to understand how to use them! Simpler solutions could be turning all of your functions into separate lua scripts and having a central program execute them one by one, round robin style. As long as the scripts don't take too long, this would probably serve your purpose. Of course if you want proper multithreading (i.e. running everything at once) then simply use multiple computers and you'll find a good deal of the technical issues just melt away. Of course that solution isn't the cheapest...
  3. Fictitious Rotor

    How could I get the current used RAM of the computer?

    So a few quick things. First, when you get a problem, please send us a screenshot and logs if possible to make it easier for us to identify your problem. Second, when you're looking at an API in the documentation, be sure to look at the examples that they give as they contain lots of hints! For example, the first snippit.lua in the computer api shows why your program doesn't work. I'll demonstrate a working solution here. Before you can call any methods, you have to assign the computer API to a variable. What they usually do in the documentation is to call the variable 'computer' like so: local computer = require("computer") print(computer.totalMemory()) Because you didn't set the api to a variable first, your program tried to call a variable that doesn't exist and gave up. Should be an easy problem to fix
  4. Fictitious Rotor

    Issues involving autorun

    Seeing as documentation is rather hard to come by for RC, I had a lengthy and highly enjoyable Easter egg hunt trying to figure out how it works - getting so far as to successfully replace autorun with it Thank you for all the help!
  5. Fictitious Rotor

    mount as an autorun

    Ah yes the '/' at the end of '/mnt/' is very important as it tells the computer that the location is a folder rather than a file. Try doing 'cd /' and then 'cd /mnt/T3' and see if that works.
  6. Fictitious Rotor

    mount as an autorun

    In fact there IS an error - it's just you can't see it Try doing local fs = require("filesystem") print(fs.mount("T3", "/T3")) And you'll see a different story! So the reason this happens is that your main drive is already mounted at "/". When you try to mount it at "/T3" then it complains... An easy way to get around this it to mount it at "/mnt/T3" like so: local fs = require("filesystem") fs.mount("T3", "/mnt/T3") Btw - you'll find that it's already in /mnt/ as well under a different name. Try doing 'ls /mnt/' In the shell to see what you've got mounted there. Good luck!
  7. Fictitious Rotor

    mount as an autorun

    Oh dear. I found the link you were talking about and I see what you mean So I believe that the '...' stands for the drive GUID or its label i.e. "277317a0-68b6-40ec-b264-d22fd76d23ff" <--- GUID Or "277" <--- Default label So seeing as my default label is "277", I can put the following in autorun.lua: local fs = require("filesystem") fs.mount("277", "/mnt/mainDrive") Now I highly doubt your hard drive will have a label of "277". If you want to get the label of your hard drive you can type 'df' Into the shell, as instructed in that link you mentioned earlier. The one you're looking for is the one with the highest available space An example if you're still confused... Good luck
  8. Fictitious Rotor

    Issues involving autorun

    Apologies for the (very) late response - got caught up in irl things somewhat! Although it saddens me that autorun isn't behaving the way it's meant to, it's certainly going to stop me tearing my hair out trying to figure out what I did wrong I'll try to figure out how to write the service as you describe and see how I can progress from there - thank you very much for your help!
  9. Fictitious Rotor

    Issues involving autorun

    Hi there, I've been messing around with some basic robots and autorun.lua. My aim was to be able to plug a floppy disk into a robot, start the robot up and have the robot copy the program that would be stored on the floppy disk. Once the file was on the internal drive, the robot would run it. The idea was that I'd be able to set the robot's functionality by hotswapping floppy disks. Trouble is, the robot autorun hasn't really been behaving. When I run the program in the shell, it works every time. However, when the robot starts up it works... sometimes. The program I told it to run just tells it to turn left - but it only does that every second boot or so (not in a regular pattern) I've been trying to figure out why this is happening for a while now and I still don't understand it! I sent the program to sleep for a few seconds to see what goes on during initialisation and found this https://imgur.com/a/WA7SK SpoooOOoky! My best guess at the moment for why it's acting up is the usage of os.execute() Although it still isn't particularly consistent with other parts of the program https://pastebin.com/9DeP5fng Here's some source code so you can have a clue what I'm on about! Oh and the robot is a collection of tier one parts with a floppy drive.
  10. Fictitious Rotor

    BIOS equivalent of 'require'

    Though all of the other answers were very informative and helpful, yours struck a chord with me in terms of clarity. Thank all you very much for spending so much time helping me out!
  11. Fictitious Rotor

    BIOS equivalent of 'require'

    I've been working on robots that don't have interfaces - and instead commune by wireless means. Part of programming these robots has involved writing on an EEPROM My problem lies with getting certain APIs. I've previously encountered things such as modem = component.proxy(component.list("modem")()) to get to an API, but FileSystem doesn't work this way. The program here (ran on a computer) wouldn't work as I put fs = require("component").filesystem Where I should have put fs = require("filesystem") If I make this change, the program works. But if I comment out the require statements, uncomment the proxy statements, write to an EEPROM and then insert into a robot, it doesn't work over there. So what's the BIOS way to get the filesystem API? (If you're wondering, the program is a recursive function designed to inform other devices of what's on the robot's filesystem)
×

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.