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

ZeroNoRyouki

Members
  • Content Count

    31
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by ZeroNoRyouki

  1. @XyFreak : I'm not making any promises because I've yet to verify if it's technically feasible, but if you would be able to "fetch a bunch of stats" with a single call, what stats would those be?
  2. What is the problem your are trying to fix?
  3. Please keep in mind that I've run all my test against OC 1.6.2.7 as that is the minimum version I'm targeting. So I don't think this is an 1.7.x problem
  4. Hi there, I've made another test tonight. I wrote a very dummy implementation for my OC API with a barebone class that's is a straight implementation of OC's Environment, SidedEnvironment and ManagedPeripheral No parent classes, no calls to the actual reactor code, just the most dummy and fast implementations of getConnected / getEnergyStored : https://pastebin.com/3Pfs1J99 An instance of that class is created when the computer port TileEntity is created and returned to OC when the cable ask the port for the SidedEnvironment capability So there is no extra code that can slo
  5. So today I put together a small ManagedPeripheral that use the same stings lookup that DE use with just a couple of methods and the delay did not go away. Implementing ManagedEnvironment and NamedBlock too changed nothing. I've also switched to the SidedEnvironment capability from the Environment one because the former is queried first by the OC cable than the latter but no luck. I've also traced how callbacks are executed by OC / Lua and the code path is identical for my owns and the DE ones. The only big differences between ER and DE at this point is that I use capabilities to int
  6. Hi there! So, I've run the "test" program in my 1.10.2 devenv and got the same bunch of 1s. I then changed getEnergyStored() to always return a fixed values without querying the reactor and tested again: same result. This is good, as it's not the reactor code that it's slowing thigs down What I basically have, code wise, is an OC'Enviroment with a bunch of @Callbacks (getEnergyStored, getFuelAmount, etc). DE also implement an Enviroment but it use a string lookup (from ManagedPeripheral) to call the methods. If OC is using reflection to find the correct method on every method invocat
×
×
  • Create New...

Important Information

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